Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bssadmin(1) [debian man page]

BSSADMIN(1)							  BP executables						       BSSADMIN(1)

NAME
bssadmin - Interplanetary Internet (IPN) scheme administration interface for use with Bundle Streaming Service SYNOPSIS
bssadmin [ commands_filename ] DESCRIPTION
bssadmin is a BSS variant of ipnadmin(1) that configures the local ION node's routing of bundles to endpoints whose IDs conform to the ipn endpoint ID scheme. ipn is a CBHE-conformant scheme; that is, every endpoint ID in the ipn scheme is a string of the form "ipn:element_number.service_number" where element_number is a CBHE "node number" and service_number identifies a specific application processing point. bssadmin operates in response to IPN scheme configuration commands found in the file commands_filename, if provided; if not, bssadmin prints a simple prompt (:) so that the user may type commands directly into standard input. The format of commands for commands_filename can be queried from bssadmin with the 'h' or '?' commands at the prompt. The commands are documented in bssrc(5). EXIT STATUS
0 Successful completion of IPN scheme administration. 1 Unsuccessful completion of IPN scheme administration, due to inability to attach to the Bundle Protocol system or to initialize the IPN scheme. EXAMPLES
bssadmin Enter interactive IPN scheme configuration command entry mode. bssadmin host1.bssrc Execute all configuration commands in host1.bssrc, then terminate immediately. FILES
See bssrc(5) for details of the BSS configuration commands for the IPN scheme. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
Note: all ION administration utilities expect source file input to be lines of ASCII text that are NL-delimited. If you edit the bssrc file on a Windows machine, be sure to use dos2unix to convert it to Unix text format before presenting it to bssadmin. Otherwise bssadmin will detect syntax errors and will not function satisfactorily. The following diagnostics may be issued to the logfile ion.log: bssadmin can't attach to BP. Bundle Protocol has not been initialized on this computer. You need to run bpadmin(1) first. bssadmin can't initialize routing database. There is no SDR data store for dtnadmin to use. Please run ionadmin(1) to start the local ION node. Can't open command file... The commands_filename specified in the command line doesn't exist. Various errors that don't cause bssadmin 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 bssrc(5) for details. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bssrc(5) perl v5.14.2 2012-05-25 BSSADMIN(1)

Check Out this Related Man Page

LTPADMIN(1)							  LTP executables						       LTPADMIN(1)

NAME
ltpadmin - ION Licklider Transmission Protocol (LTP) administration interface SYNOPSIS
ltpadmin [ commands_filename | . ] DESCRIPTION
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). EXIT STATUS
0 Successful completion of LTP administration. EXAMPLES
ltpadmin 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. FILES
See ltprc(5) for details of the LTP configuration commands. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
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. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
ltpmeter(1), ltprc(5) perl v5.14.2 2012-05-25 LTPADMIN(1)
Man Page