Provided by: ion_3.2.1+dfsg-1.1_amd64
bsspadmin - Bundle Streaming Service Protocol (BSSP) administration interface
bsspadmin [ commands_filename | . ]
bsspadmin configures, starts, manages, and stops BSSP operations for the local ION node. It operates in response to BSSP configuration commands found in the file commands_filename, if provided; if not, bsspadmin 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 bsspadmin -- that is, the ION node's bsspclock task and link service adapter tasks are stopped. The format of commands for commands_filename can be queried from bsspadmin with the 'h' or '?' commands at the prompt. The commands are documented in bssprc(5).
0 Successful completion of BSSP administration.
bsspadmin Enter interactive BSSP configuration command entry mode. bsspadmin host1.bssp Execute all configuration commands in host1.bssp, then terminate immediately. bsspadmin . Stop all BSSP operations on the local node.
See bssprc(5) for details of the BSSP 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 bssprc file on a Windows machine, be sure to use dos2unix to convert it to Unix text format before presenting it to bsspadmin. Otherwise bsspadmin will detect syntax errors and will not function satisfactorily. The following diagnostics may be issued to the logfile ion.log: bsspadmin can't attach to ION. There is no SDR data store for bsspadmin 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 bsspadmin 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 bssprc(5) for details.
Report bugs to <email@example.com>