LTPDRIVER(1)

📦 version 3.2.1, in ubuntu jammy

💅 LTPDRIVER — the LTP transmission test program, bestie edition

okay so real talk, this is ltpdriver(1) from the LTP executables squad, and she is the girl for sending test traffic over LTP. let's get into it 🦋

✨ SYNOPSIS ✨

ltpdriver remoteEngineNbr clientId nbrOfCycles greenLength [ totalLength]

🌸 DESCRIPTION 🌸

so here's the vibe. ltpdriver uses LTP to send nbrOfCycles service data units over to the ltpcounter client service process — that's the client service number clientId, attached to the remote LTP engine identified by remoteEngineNbr, mwah 😘

the length of each SDU is whatever totalLength says. if you leave totalLength out, it just defaults to 60000. no biggie.

but wait — and this is the iconic part — the trailing greenLength bytes are sent unreliably. that's the whole point of the green part. 💚

and if totalLength is 1?? absolute chaos mode, lowkey obsessed: the sizes of the transmitted service data units get randomly selected as multiples of 1024, somewhere in the range 1024 to 62464. it's giving surprise-me energy ✨

also, whenever the size of the transmitted service data unit is less than or equal to greenLength, the entire SDU gets sent unreliably. the whole thing. no reliable bits at all. periodt.

once all copies of the file have been sent, ltpdriver prints a performance report. slay, you earned it 📊

🔥 EXIT STATUS 🔥

  • "0" — ltpdriver has terminated. any problems that popped up along the way get noted in the ion.log log file, so go check there if something felt off. 👀
  • "1" — ltpdriver was unable to start, because it could not attach to the LTP protocol on the local node. the fix is easy bestie: run ltpadmin to start LTP, then try again. you got this 🫶

🎀 FILES 🎀

the service data units that ltpdriver transmits are sequences of text pulled from a file in the current working directory named "ltpdriverAduFile". and good news — ltpdriver creates that file automatically, so you don't have to lift a finger. 💅

🧚 ENVIRONMENT 🧚

No environment variables apply. that's it, that's the section. nothing here, no cap. 🙈

💀 DIAGNOSTICS 💀

diagnostic messages produced by ltpdriver get written to the ION log file ion.log. here's the full roster, no skips:

  • ltpdriver can't initialize LTP. — ltpadmin has not yet initialized LTP protocol operations. (run ltpadmin, babe.)
  • Can't create ADU file — operating system error. check errtext, correct the problem, and rerun.
  • Error writing to ADU file — operating system error. check errtext, correct the problem, and rerun.
  • ltpdriver can't create file ref. — ION system error. check for earlier diagnostic messages describing the cause of the error; correct the problem and rerun.
  • ltpdriver can't create ZCO. — ION system error. check for earlier diagnostic messages describing the cause of the error; correct the problem and rerun.
  • ltpdriver can't send message. — the LTP span to the remote engine has been stopped. 😭
  • ltp_send failed. — LTP system error. check for earlier diagnostic messages describing the cause of the error; correct the problem and rerun.

🐛 BUGS 🐛

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

👑 SEE ALSO 👑

okay that's the whole page bestie, you're officially fluent 💖

this lil manual came from perl v5.24.1, dated 2016-07-07 — vintage but still serving looks ⭐
📦 where this page comes from