sdrmend(1) [debian man page]
SDRMEND(1) ICI executables SDRMEND(1) NAME
sdrmend - SDR corruption repair utility SYNOPSIS
sdrmend sdr_name config_flags heap_words heap_key path_name DESCRIPTION
The sdrmend program simply invokes the sdr_reload_profile() function (see sdr(3)) to effect necessary repairs in a potentially corrupt SDR, e.g., due to the demise of a program that had an SDR transaction in progress at the moment it crashed. Note that sdrmend need not be run to repair ION's data store in the event of a hardware reboot: restarting ION will automatically reload the data store's profile. sdrmend is needed only when it is desired to repair the data store without requiring all ION software to terminate and restart. EXIT STATUS
0 sdrmend has terminated successfully. 1 sdrmend has terminated unsuccessfully. See diagnostic messages in the ion.log log file for details. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: Can't initialize the SDR system. Probable operations error: ION appears not to be initialized, in which case there is no point in running sdrmend. Can't reload profile for SDR. ION system error. See earlier diagnostic messages posted to ion.log for details. In this event it is unlikely that sdrmend can be run successfully, and it is also unlikely that it would have any effect if it did run successfully. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
sdr(3), ionadmin(1) perl v5.14.2 2012-05-25 SDRMEND(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)