DTN2ADMINEP(1)

📦 version 3.2.1, in ubuntu jammy

✨ DTN2ADMINEP(1) ✨

okay bestie, welcome to the manual page for dtn2adminep — it's one of the BP executables, and it's the admin endpoint girlie for the "dtn" scheme 💅

🦋 NAME 🦋

dtn2adminep — the administrative endpoint task for the "dtn" scheme, no cap 🫶

🌸 SYNOPSIS 🌸

dtn2adminep

That's it. That's the whole synopsis. She takes no arguments, she just exists 💖

⭐ DESCRIPTION ⭐

So dtn2adminep is a background "daemon" task. Main character energy, but make it invisible. What she does is receive and process administrative bundles — that's all custody signals and, nominally, all bundle status reports — that get sent to the "dtn"-scheme administrative endpoint on the local ION node. If and only if such an endpoint was established by bpadmin, though. If nobody set that up, she's just a girl standing in front of a socket that isn't there 😭

She is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of Bundle Protocol on the local ION node, and she is terminated by bpadmin in response to an 'x' (STOP) command. Also! Important! dtn2adminep can also be spawned and terminated in response to START and STOP commands that pertain specifically to the "dtn" scheme. So she's got two ways to get summoned and two ways to get sent home 🎀

Now for the actual behavior, and this part is iconic: dtn2adminep responds to custody signals as specified in the Bundle Protocol specification, RFC 5050. And she responds to bundle status reports by logging ASCII text messages describing the reported activity. Like, she's not doing anything fancy with them — she's literally writing you a little note about it in the log. Journaling queen 🦋

👑 EXIT STATUS 👑

  • "0" — dtn2adminep 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 dtn2adminep. Do not just shrug and move on, bestie, fr fr.
  • "1" — dtn2adminep was unable to attach to Bundle Protocol operations or was unable to load the "dtn" scheme database, probably because bpadmin has not yet been run. Classic "you forgot the prerequisite" moment, iykyk.

🎀 FILES 🎀

No configuration files are needed. Zero config, zero notes app, she's low maintenance.

🌈 ENVIRONMENT 🌈

No environment variables apply. She does not care what you exported. She is unbothered.

💀 DIAGNOSTICS 💀

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

  • dtn2adminep can't attach to BP. — bpadmin has not yet initialized BP operations.
  • dtn2adminep can't load routing database. — dtn2admin has not yet initialized the "dtn" scheme.
  • dtn2adminep can't get admin EID. — dtn2admin has not yet initialized the "dtn" scheme.
  • dtn2adminep crashed. — An unrecoverable database error was encountered. dtn2adminep terminates. This one is the bad one. This is the "she's gone" one. 😭

🙈 BUGS 🙈

Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> — yes that is a real email address, go off, tell them what happened 🫶

🔥 SEE ALSO 🔥

bpadmin(1), dtn2admin(1).

And that's the whole page, bestie! This one shipped as perl v5.24.1, dated 2016-07-07, and honestly? She's been doing her little admin endpoint job since then and she ate. Periodt. 💅✨

📦 where this page comes from