lgfile(5) [debian man page]

LGFILE(5)						      BP configuration files							 LGFILE(5)

NAME

       lgfile - ION Load/Go source file

DESCRIPTION

       The ION Load/Go system enables the execution of ION administrative programs at remote nodes:

	   The lgsend program reads a Load/Go source file from a local file system, encapsulates the text of that source file in a bundle, and
	   sends the bundle to a designated DTN endpoint on the remote node.

	   An lgagent task running on the remote node, which has opened that DTN endpoint for bundle reception, receives the extracted payload of
	   the bundle -- the text of the Load/Go source file -- and processes it.

       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.

       Each file capsule is structured as a single start-of-capsule line, followed by zero or more capsule text lines, followed by a single end-
       of-capsule line.  Each start-of-capsule line is of this form:

	   [file_name

       Each capsule text line can be any line of ASCII text that does not begin with an opening ([) or closing (]) bracket character.

       A text line that begins with a closing bracket character (]) is interpreted as an end-of-capsule line.

       A directive is any line of text that is not one of the lines of a file capsule and that is of this form:

	   !directive_text

       When lgagent identifies a file capsule, it copies all of the capsule's text lines to a new file named file_name that it creates in the
       current working directory.  When lgagent identifies a directive, it executes the directive by passing directive_text 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
       directive_text of a directive may reference a file that was created as the result of processing a prior file capsule line set in the same
       source file.

       Note that lgfile directives are passed to pseudoshell(), which on a VxWorks platform will always spawn a new task; the first argument in
       directive_text must be a symbol that VxWorks can resolve to a function, not a shell command.  Also note that the arguments in
       directive_text will be actual task arguments, not shell command-line arguments, so they should never be enclosed in double-quote characters
       (").  However, any argument that contains embedded whitespace must be enclosed in single-quote characters (') so that pseudoshell() can
       parse it correctly.

EXAMPLES

       Presenting the following lines of source file text to lgsend:

	   [cmd33.bprc

	   x protocol ltp

	   ]

	   !bpadmin cmd33.bprc

       should cause the receiving node to halt the operation of the LTP convergence-layer protocol.

SEE ALSO

       lgsend(1), lgagent(1), platform(3)

perl v5.14.2							    2012-05-25								 LGFILE(5)

BPTRACE(1)							  BP executables							BPTRACE(1)

NAME

       bptrace - Bundle Protocol (BP) network trace utility

SYNOPSIS

       bptrace own_endpoint_ID destination_endpoint_ID report-to_endpoint_ID TTL class_of_service "trace_text" [status_report_flags]

DESCRIPTION

       bptrace uses bp_send() to issue a single bundle to a designated destination endpoint, with status reporting options enabled as selected by
       the user, then terminates.  The status reports returned as the bundle makes its way through the network provide a view of the operation of
       the network as currently configured.

       TTL indicates the number of seconds the trace bundle may remain in the network, undelivered, before it is automatically destroyed.

       class_of_service is custody-requested.priority[.ordinal[.unreliable.critical[.flow-label]]], where custody-requested must be 0 or 1
       (Boolean), priority must be 0 (bulk) or 1 (standard) or 2 (expedited), ordinal must be 0-254, unreliable must be 0 or 1 (Boolean), critical
       must also be 0 or 1 (Boolean), and flow-label may be any unsigned integer.  ordinal is ignored if priority is not 2.  Setting
       class_of_service to "0.2.254" or "1.2.254" gives a bundle the highest possible priority.  Setting unreliable to 1 causes BP to forego
       retransmission in the event of data loss, both at the BP layer and at the convergence layer.  Setting critical to 1 causes contact graph
       routing to forward the bundle on all plausible routes rather than just the "best" route it computes; this may result in multiple copies of
       the bundle arriving at the destination endpoint, but when used in conjunction with priority 2.254 it ensures that the bundle will be
       delivered as soon as physically possible.

       trace_text can be any string of ASCII text; alternatively, if we want to send a file, it can be "@" followed by the file name.

       status_report_flags must be a sequence of status report flags, separated by commas, with no embedded whitespace.  Each status report flag
       must be one of the following: rcv, ct, fwd, dlv, del.

EXIT STATUS

       0   bptrace has terminated.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

       The following diagnostics may be issued to the ion.log log file:

       bptrace can't attach to BP.
	   bpadmin has not yet initialized BP operations.

       bptrace can't open own endpoint.
	   Another BP application task currently has own_endpoint_ID open for bundle origination and reception.  Try again after that task has
	   terminated.	If no such task exists, it may have crashed while still holding the endpoint open; the easiest workaround is to select a
	   different source endpoint.

       No space for bptrace text.
	   Probably an unrecoverable database error, in which case the local ION node must be terminated and re-initialized.

       bptrace can't create ZCO.
	   Probably an unrecoverable database error, in which case the local ION node must be terminated and re-initialized.

       bptrace can't send message.
	   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

       bp(3)

perl v5.14.2							    2012-05-25								BPTRACE(1)