DTPCCLOCK(1)

💅 DTPCCLOCK — bestie's guide to the DTPC scheduled-events daemon

okay so this is page one of the manual, section one, for dtpcclock, which lives in the DTPC executables collection. yes it's a real Unix thing. yes you're gonna understand it. let's go 🫶

---

✨ NAME ✨

dtpcclock — the DTPC daemon task whose whole job is managing scheduled events 👑

---

🌸 SYNOPSIS 🌸

dtpcclock

that's it. no flags. no arguments. she simply is. 💅

---

🦋 DESCRIPTION 🦋

okay so dtpcclock is a background "daemon" task — think of her as the girl in the group chat who actually remembers everyone's birthdays — and she periodically performs scheduled DTPC activities. every so often she just does the thing. no notes.

she does not start herself, bestie. she's spawned automatically by dtpcadmin in response to the 's' command that starts operation of the DTPC protocol. and she gets terminated by dtpcadmin in response to an 'x' (STOP) command. so dtpcadmin is basically her manager. slay.

Once per second — once. per. second. — dtpcclock takes the following action:

First she executes all DTPC events scheduled to occur at any time up to the current moment:

• DTPC ADUs for which an expected positive acknowledgment has not yet arrived are retransmitted. (like texting again because they left you on read, except it's a protocol requirement 😭)
• Received DTPC ADUs whose time to live has elapsed are deleted. (gone. expired. no more. bye 💀)

Then dtpcclock increases the ages of all DTPC ADUs pending transmission and initiates transmission of each such ADU whose age now equals or exceeds its aggregation time limit. yes she's aging them up. it's giving glow-up but for ADUs. ⭐

---

💖 EXIT STATUS 💖

• 0 — dtpcclock 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 dtpcadmin to restart dtpcclock. (so like, if you didn't tell her to leave and she left, go read the log, fix the thing, and ask dtpcadmin to bring her back 🥺)
• 1 — dtpcclock was unable to attach to DTPC protocol operations, probably because dtpcadmin has not yet been run. (she showed up to the party and the party didn't exist yet. embarrassing for everyone involved.)

---

🎀 FILES 🎀

No configuration files are needed. zero. none. she needs nothing from you. icon behavior. ✨

---

🌈 ENVIRONMENT 🌈

No environment variables apply. she does not care about your env. she is unbothered. 💅

---

👑 DIAGNOSTICS 👑

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

• dtpcclock can't initialize DTPC. — dtpcadmin has not yet initialized DTPC protocol operations. (she can't start because the setup girl hasn't set up yet.)
• Can't send finished adu. — An unrecoverable database error was encountered. dtpcclock terminates. (⚠️ she's out. not a drill.)
• Can't stop aggregation for adu. — An unrecoverable database error was encountered. dtpcclock terminates. (⚠️ same energy, different function.)
• Could not scan outbound Adus — An unrecoverable database error was encountered. dtpcclock terminates. (⚠️ database said no and she said okay bye.)

bestie. notice the pattern. "unrecoverable database error" means unrecoverable — she terminates. don't try to talk her out of it. fix the database. periodt.

---

🙈 BUGS 🙈

Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> — yes, an actual email address, from the olden times, and yes you should use it if you find something cursed. 🍓

---

🔥 SEE ALSO 🔥

• dtpcadmin(1) — her manager, her whole reason for existing, the one who starts and stops her. iykyk.

---

and that's the whole page, no cap. this documentation was brought to you by perl v5.24.1, dated 2016-07-07 — yes she's been thriving since 2016 and she's still booked and busy. 💜🧚💖

now go run her (or rather, let dtpcadmin run her, because she does NOT self-start, bestie). mwah. 💅