table of contents
- unstable 3.2.1+dfsg-1.1
ltpadmin - ION Licklider Transmission Protocol (LTP) administration interface
ltpadmin [ commands_filename | . ]
ltpadmin configures, starts, manages, and stops LTP operations for the local ION node.
It operates in response to LTP configuration commands found in the file commands_filename, if provided; if not, ltpadmin prints a simple prompt (:) so that the user may type commands directly into standard input. If commands_filename is a period (.), the effect is the same as if a command file containing the single command 'x' were passed to ltpadmin -- that is, the ION node's ltpclock task, ltpmeter tasks, and link service adapter tasks are stopped.
The format of commands for commands_filename can be queried from ltpadmin with the 'h' or '?' commands at the prompt. The commands are documented in ltprc(5).
- "0" Successful completion of LTP administration.
- Enter interactive LTP configuration command entry mode.
- ltpadmin host1.ltp
- Execute all configuration commands in host1.ltp, then terminate immediately.
- ltpadmin .
- Stop all LTP operations on the local node.
See ltprc(5) for details of the LTP configuration commands.
No environment variables apply.
Note: all ION administration utilities expect source file input to be lines of ASCII text that are NL-delimited. If you edit the ltprc file on a Windows machine, be sure to use dos2unix to convert it to Unix text format before presenting it to ltpadmin. Otherwise ltpadmin will detect syntax errors and will not function satisfactorily.
The following diagnostics may be issued to the logfile ion.log:
- ltpadmin can't attach to ION.
- There is no SDR data store for ltpadmin to use. You should run ionadmin(1) first, to set up an SDR data store for ION.
- Can't open command file...
- The commands_filename specified in the command line doesn't exist.
Various errors that don't cause ltpadmin to fail but are noted in the ion.log log file may be caused by improperly formatted commands given at the prompt or in the commands_filename file. Please see ltprc(5) for details.
Report bugs to <email@example.com>