Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

lgagent(1) [debian man page]

LGAGENT(1)							  BP executables							LGAGENT(1)

NAME
lgagent - ION Load/Go remote agent program SYNOPSIS
lgagent own_endpoint_ID DESCRIPTION
ION Load/Go is a system for management of an ION-based network, enabling the execution of ION administrative programs at remote nodes. The system comprises two programs, lgsend and lgagent. The lgagent task on a given node opens the indicated ION endpoint for bundle reception, receives the extracted payloads of Load/Go bundles sent to it by lgsend as run on one or more remote nodes, and processes those payloads, which are the text of Load/Go source files. Load/Go source file content is limited to newline-terminated lines of ASCII characters. More specifically, the text of any Load/Go source file is a sequence of line sets of two types: file capsules and directives. Any Load/Go source file may contain any number of file capsules and any number of directives, freely intermingled in any order, but the typical structure of a Load/Go source file is simply a single file capsule followed by a single directive. When lgagent identifies a file capsule, it copies all of the capsule's text lines to a new file that it creates in the current working directory. When lgagent identifies a directive, it executes the directive by passing the text of the directive to the pseudoshell() function (see platform(3)). lgagent processes the line sets of a Load/Go source file in the order in which they appear in the file, so the text of a directive may reference a file that was created as the result of processing a prior file capsule in the same source file. EXIT STATUS
0 Load/Go remote agent processing has terminated. FILES
lgfile contains the Load/Go file capsules and directives that are to be processed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: lgagent: can't attach to BP. Bundle Protocol is not running on this computer. Run bpadmin(1) to start BP. lgagent: can't open own endpoint. own_endpoint_ID is not a declared endpoint on the local ION node. Run bpadmin(1) to add it. lgagent: bundle reception failed. ION system problem. Investigate and correct before restarting. lgagent cannot continue. lgagent processing problem. See earlier diagnostic messages for details. Investigate and correct before restarting. lgagent: no space for bundle content. ION system problem: have exhausted available SDR data store reserves. lgagent: can't receive bundle content. ION system problem: have exhausted available SDR data store reserves. lgagent: can't handle bundle delivery. ION system problem. Investigate and correct before restarting. lgagent: pseudoshell failed. Error in directive line, usually an attempt to execute a non-existent administration program (e.g., a misspelled program name). Terminates processing of source file content. A variety of other diagnostics noting source file parsing problems may also be reported. These errors are non-fatal but they terminate the processing of the source file content from the most recently received bundle. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
lgsend(1), lgfile(5) perl v5.14.2 2012-05-25 LGAGENT(1)

Check Out this Related Man Page

BPCHAT(1)							  BP executables							 BPCHAT(1)

NAME
bpchat - Bundle Protocol chat test program SYNOPSIS
bpchat sourceEID destEID [ct] DESCRIPTION
bpchat uses Bundle Protocol to send input text in bundles, and display the payload of received bundles as output. It is similar to the talk utility, but operates over the Bundle Protocol. It operates like a combination of the bpsource and bpsink utilities in one program (unlike bpsource, bpchat emits bundles with a sourceEID). If the sourceEID and destEID are both bpchat applications, then two users can chat with each other over the Bundle Protocol: lines that one user types on the keyboard will be transported over the network in bundles and displayed on the screen of the other user (and the reverse). bpchat terminates upon receiving the SIGQUIT signal, i.e., ^C from the keyboard. EXIT STATUS
0 bpchat has terminated normally. Any problems encountered during operation will be noted in the ion.log log file. 1 bpchat has terminated due to a BP transmit or reception failure. Details should be noted in the ion.log log file. OPTIONS
[ct] If the string "ct" is appended as the last argument, then bundles will be sent with custody transfer requested. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
Diagnostic messages produced by bpchat are written to the ION log file ion.log. Can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. Can't open own endpoint. Another application has already opened ownEndpointId. Terminate that application and rerun. bpchat bundle reception failed. BP system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. No space for ZCO extent. ION system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. Can't create ZCO. ION system error. Check for earlier diagnostic messages describing the cause of the error; correct problem and rerun. bpchat can't send echo bundle. BP 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
bpecho(1), bpsource(1), bpsink(1), bp(3) perl v5.14.2 2012-05-25 BPCHAT(1)
Man Page