bpclock(1) [debian man page]
BPCLOCK(1) BP executables BPCLOCK(1) NAME
bpclock - Bundle Protocol (BP) daemon task for managing scheduled events SYNOPSIS
bpclock DESCRIPTION
bpclock is a background "daemon" task that periodically performs scheduled Bundle Protocol activities. It is spawned automatically by bpadmin in response to the 's' 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. Once per second, bpclock takes the following action: First it (a) destroys all bundles whose TTLs have expired, (b) enqueues for re-forwarding all bundles that were expected to have been transmitted (by convergence-layer output tasks) by now but are still stuck in their assigned transmission queues, and (c) enqueues for re-forwarding all bundles for which custody has not yet been taken that were expected to have been received and acknowledged by now (as noted by invocation of the bpMemo() function by some convergence-layer adapter that had CL-specific insight into the appropriate interval to wait for custody acceptance). Then bpclock adjusts the transmission and reception "throttles" that control rates of LTP transmission to and reception from neighboring nodes, in response to data rate changes as noted in the RFX database by rfxclock. bpclock then checks for bundle origination activity that has been blocked due to insufficient allocated space for BP traffic in the ION data store: if space for bundle origination is now available, bpclock gives the bundle production throttle semaphore to unblock that activity. Finally, bpclock applies rate control to all convergence-layer protocol inducts and outducts: For each induct, bpclock increases the current capacity of the duct by the applicable nominal data reception rate. If the revised current capacity is greater than zero, bpclock gives the throttle's semaphore to unblock data acquisition (which correspondingly reduces the current capacity of the duct) by the associated convergence layer input task. For each outduct, bpclock increases the current capacity of the duct by the applicable nominal data transmission rate. If the revised current capacity is greater than zero, bpclock gives the throttle's semaphore to unblock data transmission (which correspondingly reduces the current capacity of the duct) by the associated convergence layer output task. EXIT STATUS
0 bpclock 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 bpadmin to restart bpclock. 1 bpclock was unable to attach to Bundle Protocol operations, probably because bpadmin 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: bpclock can't attach to BP. bpadmin has not yet initialized BP operations. Can't dispatch events. An unrecoverable database error was encountered. bpclock terminates. Can't adjust throttles. An unrecoverable database error was encountered. bpclock terminates. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), rfxclock(1) perl v5.14.2 2012-05-25 BPCLOCK(1)
Check Out this Related Man Page
DGRCLA(1) BP executables DGRCLA(1) NAME
dgrcla - DGR-based BP convergence layer adapter (input and output) task SYNOPSIS
dgrcla local_hostname[:local_port_nbr] DESCRIPTION
dgrcla is a background "daemon" task that spawns two threads, one that handles DGR convergence layer protocol input and a second that handles DGR convergence layer protocol output. The input thread receives DGR messages via a UDP socket bound to local_hostname and local_port_nbr, extracts bundles from those messages, and passes them to the bundle protocol agent on the local ION node. (local_port_nbr defaults to 1113 if not specified.) The output thread extracts bundles from the queues of bundles ready for transmission via DGR to remote bundle protocol agents, encapsulates them in DGR messages, and sends those messages to the appropriate remote UDP sockets as indicated by the host names and UDP port numbers (destination induct names) associated with the bundles by the routing daemons that enqueued them. Note that dgrcla is a "promiscuous" convergence layer daemon, able to transmit bundles to any DGR destination induct. Its duct name is the name of the corresponding induct, rather than the induct name of any single DGR destination induct to which it might be dedicated, so scheme configuration directives that cite this outduct must provide destination induct IDs. For the DGR convergence-layer protocol, destination induct IDs are identical to induct names, i.e., they are of the form local_hostname[:local_port_nbr]. dgrcla is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of the Bundle Protocol, and it is terminated by bpadmin in response to an 'x' (STOP) command. dgrcla can also be spawned and terminated in response to START and STOP commands that pertain specifically to the DGR convergence layer protocol. EXIT STATUS
0 dgrcla terminated normally, 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 bpadmin to restart dgrcla. 1 dgrcla terminated abnormally, for reasons noted in the ion.log file. Investigate and solve the problem identified in the log file, then use bpadmin to restart dgrcla. FILES
No configuration files are needed. ENVIRONMENT
No environment variables apply. DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file: dgrcla can't attach to BP. bpadmin has not yet initialized Bundle Protocol operations. No such dgr induct. No DGR induct with duct name matching local_hostname and local_port_nbr has been added to the BP database. Use bpadmin to stop the DGR convergence-layer protocol, add the induct, and then restart the DGR protocol. CLI task is already started for this engine. Redundant initiation of dgrcla. No such dgr induct. No DGR outduct with duct name matching local_hostname and local_port_nbr has been added to the BP database. Use bpadmin to stop the DGR convergence-layer protocol, add the outduct, and then restart the DGR protocol. Can't get IP address for host Operating system error. Check errtext, correct problem, and restart DGR. dgrcla can't open DGR service access point. DGR system error. Check prior messages in ion.log log file, correct problem, and then stop and restart the DGR protocol. dgrcla can't create sender thread Operating system error. Check errtext, correct problem, and restart DGR. dgrcla can't create receiver thread Operating system error. Check errtext, correct problem, and restart DGR. BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
bpadmin(1), bprc(5) perl v5.14.2 2012-05-25 DGRCLA(1)