RFXCLOCK(1)

📦 version 3.2.1, in ubuntu jammy

💖 RFXCLOCK 💖 — the ION daemon task for managing scheduled events

okay bestie, welcome to rfxclock(1), part of the ICI executables family. she's a lil background girlie with a big job and honestly? she eats. 🎀

✨ NAME ✨

rfxclock — ION daemon task for managing scheduled events

🦋 SYNOPSIS 🦋

rfxclock

that's it. that's the whole vibe. no flags, no args, she just goes. 💅

🌸 DESCRIPTION 🌸

so rfxclock is a background "daemon" task — your classic unseen main character — and what she does is periodically apply scheduled changes in node connectivity and range to the ION node's database. lowkey the backbone of the whole operation ngl.

she is spawned automatically by ionadmin in response to the 's' command that starts operation of the ION node infrastructure. and she is terminated by ionadmin in response to an 'x' (STOP) command. so basically ionadmin is her manager and she does not take meetings. 😌

Once per second, rfxclock takes the following action — three lil steps, in order, no skipping:

  1. 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. like, hi bestie, are you emotionally available for custody yet? 🙈
  2. Then rfxclock purges the database of all range and contact information that is no longer applicable, based on the stop times of the records. bye, expired records, you were iconic. 💀
  3. 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. fresh, current, on-time. periodt. ✨

👑 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. she's low-maintenance, she's self-sufficient, she's literally that girl. 💖

🌈 ENVIRONMENT 🌈

No environment variables apply. nothing to set, nothing to export, we simply vibe. 🧚

💜 DIAGNOSTICS 💜

The following diagnostics may be issued to the ion.log log file — so if something's giving drama, that's where the receipts are:

  • 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.
bestie if you see "unrecoverable database error" that's not a soft launch, that's a full shutdown. rfxclock terminates, no cap. go read the log. 🔥

🍓 BUGS 🍓

Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> — yes, fr fr, that's the actual address, go tell them everything. 🫶

⭐ SEE ALSO ⭐

and that's the whole page, bestie!! 💅 this one shipped as part of perl v5.24.1, dated 2016-07-07 — vintage but still serving looks. mwah, go forth and schedule your events responsibly. 🎀✨💖

📦 where this page comes from