CFDPCLOCK(1)

πŸ“¦ version 3.2.1, in ubuntu jammy

πŸ’– CFDPCLOCK(1) πŸ’–

okay bestie, welcome to the CFDP executables manual page, this one's all about cfdpclock and honestly? she's the quiet one in the back keeping everything on schedule. πŸ•βœ¨


✨ NAME ✨

cfdpclock β€” CFDP daemon task for managing scheduled events


🌸 SYNOPSIS 🌸

cfdpclock

that's it. no flags, no args, she just is. πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

cfdpclock is a background "daemon" task that periodically performs scheduled CFDP activities. lowkey the backbone of the whole operation. πŸ’…

She gets spawned automatically by cfdpadmin when it gets the 's' command that starts operation of the CFDP protocol, and she gets terminated by cfdpadmin when it gets an 'x' (STOP) command. so like, cfdpadmin is literally her whole support system, iykyk. 🫢

Once per second β€” yes, every single second, she does not skip leg day β€” cfdpclock takes the following action:

  1. First she scans all inbound file delivery units (FDUs). For each one whose check timeout deadline has passed, she increments the check timeout count and resets the check timeout deadline. and for each one whose check timeout count exceeds the limit configured for this node, she invokes the Check Limit Reached fault handling procedure. she's watching. she always is. πŸ‘€
  2. Then she scans all outbound FDUs. For each one that has been Canceled, she cancels all extant PDU bundles and sets transmission progress to the size of the file, simulating the completion of transmission. then she destroys each outbound FDU whose transmission is completed. clean up, no drama, periodt. 🧹✨

πŸ’€ EXIT STATUS πŸ’€

  • "0" β€” cfdpclock terminated, for reasons noted in the ion.log file. and bestie, if this termination was not commanded? investigate, solve the problem identified in the log file, and use cfdpadmin to restart cfdpclock. don't just ignore her, she's trying her best. 😭
  • "1" β€” cfdpclock was unable to attach to CFDP protocol operations, probably because cfdpadmin has not yet been run. she's knocking on the door and nobody's home. πŸšͺπŸ™ˆ

πŸŽ€ FILES πŸŽ€

No configuration files are needed. she's low maintenance, we love that for her. πŸ’–


🌈 ENVIRONMENT 🌈

No environment variables apply. nothing to set up, nothing to export, just vibes. ✨


πŸ”₯ DIAGNOSTICS πŸ”₯

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

  • cfdpclock can't initialize CFDP. β€” cfdpadmin has not yet initialized CFDP protocol operations. girl can't start the party if nobody set up the venue. πŸ₯²
  • Can't dispatch events. β€” An unrecoverable database error was encountered. cfdpclock terminates. πŸ’€
  • Can't manage links. β€” An unrecoverable database error was encountered. cfdpclock terminates. πŸ’€
ngl those last two are giving "the database said no and there is no plan B" energy. when she terminates, she terminates. πŸͺ¦

πŸ› BUGS πŸ›

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

(please be nice to her, she's doing scheduled events in the background at 1 Hz and she deserves respect fr fr 🫢)


πŸ‘‘ SEE ALSO πŸ‘‘

cfdpadmin(1) β€” her ride or die, the one who spawns her and stops her. iconic duo, no cap. πŸ’œ


okay and that's the whole page!! this was CFDPCLOCK(1) from the CFDP executables era, dated 2016-07-07 and rendered with perl v5.24.1 πŸ’…πŸŒΈ β€” thanks for reading bestie, go keep your scheduled events on lock, mwah πŸŽ€πŸ’–βœ¨

πŸ“¦ where this page comes from