rfxclock(1) [debian man page]

RFXCLOCK(1)							  ICI executables						       RFXCLOCK(1)

NAME

       rfxclock - ION daemon task for managing scheduled events

SYNOPSIS

       rfxclock

DESCRIPTION

       rfxclock is a background "daemon" task that periodically applies scheduled changes in node connectivity and range to the ION node's
       database.  It is spawned automatically by ionadmin in response to the 's' command that starts operation of the ION node infrastructure, and
       it is terminated by ionadmin in response to an 'x' (STOP) command.

       Once per second, rfxclock takes the following action:

	   For each neighboring node that has been refusing custody of bundles sent to it to be forwarded to some destination node, to which no
	   such bundle has been sent for at least N seconds (where N is twice the one-way light time from the local node to this neighbor),
	   rfxclock turns on a probeIsDue flag authorizing transmission of the next such bundle in hopes of learning that this neighbor is now
	   able to accept custody.

	   Then rfxclock purges the database of all range and contact information that is no longer applicable, based on the stop times of the
	   records.

	   Finally, rfxclock applies to the database all range and contact information that is currently applicable, i.e., those records whose
	   start times are before the current time and whose stop times are in the future.

EXIT STATUS

       0   rfxclock terminated, for reasons noted in the ion.log file.	If this termination was not commanded, investigate and solve the problem
	   identified in the log file and use ionadmin to restart rfxclock.

       1   rfxclock was unable to attach to the local ION node, probably because ionadmin has not yet been run.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

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

       rfxclock can't attach to ION.
	   ionadmin has not yet initialized the ION database.

       Can't apply ranges.
	   An unrecoverable database error was encountered.  rfxclock terminates.

       Can't apply contacts.
	   An unrecoverable database error was encountered.  rfxclock terminates.

       Can't purge ranges.
	   An unrecoverable database error was encountered.  rfxclock terminates.

       Can't purge contacts.
	   An unrecoverable database error was encountered.  rfxclock terminates.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       ionadmin(1)

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

BSSFW(1)							  BP executables							  BSSFW(1)

NAME

       bssfw - bundle route computation task for the IPN scheme, adapted for Bundle Streaming Service

SYNOPSIS

       bssfw

DESCRIPTION

       bssfw is a background "daemon" task that pops bundles from the queue of bundle destined for IPN-scheme endpoints, computes proximate
       destinations for those bundles, and appends those bundles to the appropriate queues of bundles pending transmission to those computed
       proximate destinations.

       For each possible proximate destination (that is, neighboring node) there is a separate queue for each possible level of bundle priority:
       0, 1, 2.  Each outbound bundle is appended to the queue matching the bundle's designated priority.

       Proximate destination computation is affected by static and default routes as configured by bssadmin(1) and by contact graphs as managed by
       ionadmin(1) and rfxclock(1).  bssfw differs from ipnfw in this way: a bundle that is destined for an endpoint associated with a BSS
       application (as registered in an "entry" passed to bssadmin(1) in a bssrc(5) command) is forwarded via a duct identified in a separately
       defined real-time or playback duct expression, rather than the standard duct that is used for non-BSS traffic.

       bssfw is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of Bundle Protocol on the local ION
       node, and it is terminated by bpadmin in response to an 'x' (STOP) command.  bssfw can also be spawned and terminated in response to START
       and STOP commands that pertain specifically to the IPN scheme.

EXIT STATUS

       0   bssfw terminated, for reasons noted in the ion.log log file.  If this termination was not commanded, investigate and solve the problem
	   identified in the log file and use bpadmin to restart bssfw.

       1   bssfw could not commence operations, for reasons noted in the ion.log log file.  Investigate and solve the problem identified in the
	   log file, then use bpadmin to restart bssfw.

FILES

       No configuration files are needed.

ENVIRONMENT

       No environment variables apply.

DIAGNOSTICS

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

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

       bssfw can't load routing database.
	   bssadmin has not yet initialized the IPN scheme.

       Can't create lists for route computation.
	   An unrecoverable database error was encountered.  bssfw terminates.

       'bss' scheme is unknown.
	   The IPN scheme was not added when bpadmin initialized BP operations.  Use bpadmin to add and start the scheme.

       Can't take forwarder semaphore.
	   ION system error.  bssfw terminates.

       Can't exclude sender from routes.
	   An unrecoverable database error was encountered.  bssfw terminates.

       Can't enqueue bundle.
	   An unrecoverable database error was encountered.  bssfw terminates.

BUGS

       Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>

SEE ALSO

       bpadmin(1), bssadmin(1), bprc(5), bssrc(5).

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