ltpcounter(1) [debian man page]
LTPCOUNTER(1) LTP executables LTPCOUNTER(1) NAME
ltpcounter - LTP reception test program SYNOPSIS
ltpcounter client_ID [max_nbr_of_bytes] DESCRIPTION
ltpcounter uses LTP to receive service data units flagged with client service number client_ID from a remote ltpdriver client service process. When the total number of bytes of client service data it has received exceeds max_nbr_of_bytes, it terminates and prints reception and cancellation statistics. If max_nbr_of_bytes is omitted, the default limit is 2 billion bytes. While receiving data, ltpcounter prints a 'v' character every 5 seconds to indicate that it is still alive. EXIT STATUS
0 ltpcounter has terminated. Any problems encountered during operation will be noted in the ion.log log file. 1 ltpcounter was unable to start, because it could not attach to the LTP protocol on the local node or could not open access to client service clientId. In the former case, run ltpadmin to start LTP and try again. In the latter case, some other client service task has already opened access to client service clientId. If no such task is currently running (e.g., it crashed while holding the client service open), use ltpadmin to stop and restart the LTP protocol. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
Diagnostic messages produced by ltpcounter are written to the ION log file ion.log. ltpcounter can't initialize LTP. ltpadmin has not yet initialized LTP protocol operations. ltpcounter can't open client access. Another task has opened access to service client clientId and has not yet relinquished it. Can't get LTP notice. LTP system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
ltpadmin(1), ltpdriver(1), ltp(3) perl v5.14.2 2012-05-25 LTPCOUNTER(1)
Check Out this Related Man Page
UDPLSI(1) LTP executables UDPLSI(1) NAME
udplsi - UDP-based LTP link service input task SYNOPSIS
udplsi {local_hostname | @}[:local_port_nbr] DESCRIPTION
udplsi is a background "daemon" task that receives UDP datagrams via a UDP socket bound to local_hostname and local_port_nbr, extracts LTP segments from those datagrams, and passes them to the local LTP engine. Host name "@" signifies that the host name returned by hostname(1) is to be used as the socket's host name. If not specified, port number defaults to 1113. The link service input task is spawned automatically by ltpadmin in response to the 's' command that starts operation of the LTP protocol; the text of the command that is used to spawn the task must be provided as a parameter to the 's' command. The link service input task is terminated by ltpadmin in response to an 'x' (STOP) command. EXIT STATUS
0 udplsi terminated normally, for reasons noted in the ion.log file. If this termination was not commanded, investigate and solve the problem identified in the log file and use ltpadmin to restart udplsi. 1 udplsi terminated abnormally, for reasons noted in the ion.log file. Investigate and solve the problem identified in the log file, then use ltpadmin to restart udplsi. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: udplsi can't initialize LTP. ltpadmin has not yet initialized LTP protocol operations. LSI task is already started. Redundant initiation of udplsi. LSI can't open UDP socket Operating system error. Check errtext, correct problem, and restart udplsi. LSI can't initialize socket Operating system error. Check errtext, correct problem, and restart udplsi. LSI can't create receiver thread Operating system error. Check errtext, correct problem, and restart udplsi. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
ltpadmin(1), udplso(1), owltsim(1) perl v5.14.2 2012-05-25 UDPLSI(1)