BPCLOCK(1)

💖 BPCLOCK(1) 💖

part of the BP executables crew 🦋 (BP = Bundle Protocol, iykyk)

---

✨ NAME ✨

bpclock — the Bundle Protocol (BP) daemon task whose whole job is managing scheduled events 💅

---

🌸 SYNOPSIS 🌸

bpclock

that's it bestie, no args, no flags, no nothing, she just goes 🎀

---

👑 DESCRIPTION 👑

okay so bpclock is a background "daemon" task and she periodically does all the scheduled Bundle Protocol activities. very main character, very self-sufficient. she is spawned automatically by bpadmin when you hit it with the 's' command that starts operation of Bundle Protocol on the local ION node, and she gets terminated by bpadmin when you hit it with an 'x' (STOP) command. so basically bpadmin is her mom fr fr.

once per second, bpclock does the following:

1. First she does a little trio of chores, no biggie:
   • (a) she destroys all bundles whose TTLs have expired 💀 like okay they're dead, let them go
   • (b) she 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 — stuck?? not on her watch
   • (c) she 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)
2. 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. glow up for your data rates ✨
3. Then she 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. unblocked and thriving 🫶
4. 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.

semaphores given, capacities adjusted, vibes immaculate 🌈

---

💅 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. like bestie she didn't just leave for no reason, check the log 😭
• "1" — bpclock was unable to attach to Bundle Protocol operations, probably because bpadmin has not yet been run. run bpadmin first, babe 🙈

---

🎀 FILES 🎀

No configuration files are needed. zero config, zero stress, we love that for her 🦋

---

🍓 ENVIRONMENT 🍓

No environment variables apply. none. nada. she doesn't read them, don't bother 💜

---

⭐ 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> — they wanna hear from you, fr fr 🫶

---

🌈 SEE ALSO 🌈

• bpadmin(1)
• rfxclock(1)

---

and that's the whole page bestie, no notes, you ate 💅✨

this was perl v5.24.1, dated 2016-07-07 — iconic behavior honestly, she's been serving since 2016 and she's still clocking in every second 🕐👑 bye!! 💖🦋🌸