LTPCLO(1)

💖 ltpclo — the LTP-based BP convergence layer adapter output task 💖

okay bestie, welcome to the LTPCLO(1) page, from the BP executables manual section. this one's a lil background daemon with main character energy and a very specific job. let's get into it 🦋

---

✨ SYNOPSIS ✨

ltpclo [-]remote_node_nbr

---

🌸 DESCRIPTION 🌸

so like. ltpclo is a background "daemon" task (yes the quotes are load-bearing, it's giving daemon-but-make-it-casual 💅). what it does is it pulls bundles out of the queues of segments that are ready to be transmitted via LTP, and ships them over to the remote bundle protocol agent that's identified by remote_node_nbr. then it hands them to the local LTP engine which does the aggregation, segmentation, and transmission thing to the remote node. that's the whole vibe.

now here's the tea 🍵 — if remote_node_nbr has a - character in front of it, then every single LTP transmission ltpclo does will be "green", aka unreliable transmission. no acknowledgment, no retransmission. it just yolo-sends it. no cap.

ngl, also important: ltpclo is not a "promiscuous" convergence layer daemon. it can transmit bundles only to the node it's configured for, periodt. so any scheme configuration directives that cite this outduct only need to give the protocol name and the outduct name (that's the remote node number) exactly as specified on the command line when ltpclo was started. that's it, that's the whole config situation.

and how does it even get born? 👶 ltpclo is spawned automatically by bpadmin in response to the 's' (START) command that starts operation of the Bundle Protocol, and it gets terminated by bpadmin in response to an 'x' (STOP) command. it can also be spawned and terminated in response to START and STOP commands that pertain specifically to the LTP convergence layer protocol. so like, two ways in, two ways out. iconic.

---

🔥 EXIT STATUS 🔥

• "0" — ltpclo terminated normally, for reasons noted in the ion.log file. if this termination was not commanded, bestie please investigate and solve the problem identified in the log file and use bpadmin to restart the BRSC protocol. don't just ignore it 😭
• "1" — ltpclo terminated abnormally, for reasons noted in the ion.log file. investigate and solve the problem identified in the log file, then use bpadmin to restart the BRSC protocol.

---

🎀 FILES 🎀

no configuration files are needed. literally none. we love a low-maintenance queen ✨

---

🌈 ENVIRONMENT 🌈

no environment variables apply. zero. zilch. nothing to memorize here, you're welcome 🫶

---

💜 DIAGNOSTICS 💜

these are the diagnostics that may be issued to the ion.log log file:

• ltpclo can't attach to BP. — bpadmin has not yet initialized Bundle Protocol operations.
• No such ltp duct. — no LTP outduct with a duct name matching remote_node_nbr has been added to the BP database. use bpadmin to stop the LTP convergence-layer protocol, add the outduct, and then restart the LTP protocol. (yes, in that order, don't freestyle it 💅)
• CLO task is already started for this duct. — redundant initiation of ltpclo. it's already up, bestie, chill.
• ltpclo can't initialize LTP. — ltpadmin has not yet initialized LTP operations.

---

🐛 BUGS 🐛

found a bug? report it to <ion-bugs@korgano.eecs.ohiou.edu> — they wanna hear about it fr fr.

---

👑 SEE ALSO 👑

bpadmin(1), bprc(5), ltpadmin(1), ltprc(5), ltpcli(1)

---

and that's the whole page, bestie 🌸 this one's from perl v5.24.1, dated 2016-07-07 — yeah she's a little vintage but she still slays 💖 mwah, go forth and transmit responsibly ✨🎀🦋