UDPBSO(1)

📦 version 3.2.1, in ubuntu jammy

💖 UDPBSO(1) — bestie edition 💖

BSSP executables · the manual page for udpbso

okay so. you wanna know about udpbso? bucket hat on, snacks out, because this one is lowkey the post office of your BSSP setup and she is serving. let's get into it. 🎀

✨ NAME ✨

udpbso</purl> — the UDP-based best-effort link service output task for BSSP. she takes segments, she wraps them in UDP, she ships them. that's the whole job. iconic. 💅

🌸 SYNOPSIS 🌸

udpbso {remote_engine_hostname | @}[:remote_port_nbr] txbps
remote_engine_nbr

🦋 DESCRIPTION 🦋

So. udpbso is a background "daemon" task, and her whole personality is this: she reaches into the queue of segments that are headed for the remote BSSP engine you named, pulls them out, wraps each one up in a UDP datagram, and sends those datagrams off to the UDP port on the host you pointed at. if you don't say which port, she just assumes 6001. default queen behavior. no cap. ✨

UDP congestion is a whole thing, and you can control it by setting udpbso's rate of UDP datagram transmission, txbps (that's transmission rate in bits per second, bestie, keep up 💖), to a value that your underlying network can actually handle. don't overfeed her. she will not be ok.

Every single "span" of BSSP data interchange between the local BSSP engine and a neighboring BSSP engine needs its own best-effort and reliable link service output tasks. and like — good news — all link service output tasks get spawned automatically by bsspadmin when you hit it with the 's' command that starts operation of the BSSP protocol. and when you send the 'x' (STOP) command, bsspadmin terminates all of them. no manual labor required, we love a hands-off situation. 🙈

💜 EXIT STATUS 💜

  • "0" — udpbso terminated normally, for reasons noted in the ion.log file. now listen: if this termination was not commanded by you, do not just shrug and move on. investigate, solve the problem identified in the log file, and use bsspadmin to restart udpbso. 🫶
  • "1" — udpbso terminated abnormally, for reasons noted in the ion.log file. investigate and solve the problem identified in the log file, then use bsspadmin to restart udpbso. 😭

🎀 FILES 🎀

No configuration files are needed. zero. none. she comes as she is. ✨

🌈 ENVIRONMENT 🌈

No environment variables apply. nothing to export, nothing to source, nothing to forget. bless. 🧚

👑 DIAGNOSTICS 👑

The following diagnostics may be issued to the ion.log log file — aka the group chat where she tells you what's wrong:

  • udpbso can't initialize BSSP. — bsspadmin has not yet initialized BSSP protocol operations. she's waiting on somebody else to go first. 💀
  • No such engine in database. — remote_engine_nbr is invalid, or the applicable span has not yet been added to the BSSP database by bsspadmin. wrong number, bestie.
  • BE-BSO task is already started for this engine. — redundant initiation of udpbso. she's already here. she's already on the clock. 🫠
  • BE-BSO can't open UDP socket — operating system error. check errtext, correct problem, and restart udpbso.
  • BE-BSO can't bind UDP socket — operating system error. check errtext, correct problem, and restart udpbso.
  • Segment is too big for UDP BSO. — configuration error: segments that are too large for UDP transmission (i.e., larger than 65535 bytes) are being enqueued for udpbso. use bsspadmin to change maximum segment size for this span. that segment is not fitting in these jeans. 💅

💀 BUGS 💀

Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>. fr fr, they want to hear about it. 🍓

🔥 SEE ABSO 🔥

and that's the whole page, bestie!! this was UDPBSO(1) from the BSSP executables collection, and the page itself was generated by perl v5.24.1 back on 2016-07-07. she's been iconic since 2016 and she's not slowing down. periodt. 👑✨💖

📦 where this page comes from