LDMPING

ldmping - check if ldm server is running

ldmping [−x] [−v|−q] [−l logdest] [−ttimeout] [−iinterval] [−hremote] [remote...]

This program sends a RPC NULLPROC request to a list of LDM servers remote .... The default behavior of the program changes depending on whether the program is invoked interactively or not. (This is determined by whether STDERR "isatty".)

This program is used as a simple check that an LDM server is running on a given host and that the server is responding to RPC calls, or to perform this check on a group of hosts.

−v

Verbose flag. If the verbose flag is on, a log message is emitted on success as well as failure. If the program is invoked interactively, this is the default.

−q

Quiet, turn off verbose flag. Useful to override the default.

−l logdest

Log to logdest. One of ’’ (system logging daemon), ’-’ (standard error stream), or file logdest. Default is the standard error stream if the process has a controlling terminal (i.e., the process isn’t a daemon); otherwise, either the LDM log file or the system logging daemon (execute this program with just the option ’-?’ to determine which).

−t timeout

Set the RPC timeout to this many seconds. The default is 10 seconds.

−i interval

Set the polling interval to this many seconds. If non zero, the program will loop forever (until interrupted). If zero, the program tries each remote once, exiting with status 0 if all check out okay, otherwise exiting with status one (failure) when an error is encountered. The default polling interval is 25 when interactive and 0 otherwise.

−h remote

Requests that that the LDM server on remote be pinged. Multiple remotes may be specified. A list of remotes may be also specified without using "-h". If no remotes are specified, defaults to "localhost".

−x

Requests that debugging information also be printed. (None in this program.)

The report consists of 5 fields.

The first field is the state of the connection. The connection may be seen as climbing through various states to complete a transaction. The lowest state is NAMED, we have defined a service we wish to contact (the ldm via TCP at a given remotehost). The next state is ADDRESSED, meaning we were able to translate the hostname into an IP address. (Sometimes RPC problems are really nameservice problems.) The third state, PMAP_CLNTED, indicates that the RPC portmapper is up on the remote and the fourth, MAPPED, indicates that there is ldm service (program 300029) registered. The fifth state is H_CLNTED, indicating that we were able to make a TCP connection to the port handed us by the RPC portmapper. Presumably this is a connection to an ldm server. Finally, if the remote service responds to the RPC NULLPROC within the timeout interval, we mark it as RESPONDING.

The second field is the time elapsed in completing the call. Expect that the Elapsed is greater during the initial connection than during subsequent calls, since this time includes all the time taken to climb thru the states.

The third field is the TCP port number (returned by the RPC portmapper).

The fourth field is the remote host you specified.

If there is an RPC problem, the RPC status will be printed at the end of the line. Note that this status may apply to the RPC portmapper if the state is lower than CONNECTED.

ldmd(1), ingestd(1), ulog(3), rpcinfo(1)