NOTE - If your application will be using
the netmgt_kill_request2(3n) function, you need to call netmgt_set_manager_id
(3n) right after calling netmgt_set_instance(3n). See
Section 4.7, "Stopping Requests," on page 4-8
, for more information about netmgt_kill_request2(3n).
Count |
Interval |
Interpretation |
When you send the request, you will get
a reply from the Manager Services library indicating the status of the request.
If the request was accepted by the agent, you will get a UNIX timestamp you
can use to identify the request when you get reports or want to kill the request.
If the request timestamp was NULL, either the agent didn't accept
the request or there was an error sending the message to the agent. You can
call netmgt_fetch_error(3n), discussed below, for more information
on handling errors.
NOTE - Requests are identified
by the agent host's IP address and the timestamp of the request.
NOTE - You cannot use netmgt_kill_request2(3n) to kill requests started by an agent created with Site/SunNet/Domain Manager version 1.x agent services libraries. Upon receiving a netmgt_kill_request2(3n) call, SunNet Manager 1.x agents will return FALSE and set the service error to NETMGT_UNKNOWNREQUEST. To work properly with 1.x agents, your application should call netmgt_kill_requests(3n), which is understood by all versions of Site/SunNet/Domain Manager agents.