FILE2SDR(1)

📦 version 3.2.1, in ubuntu jammy

💖 file2sdr — SDR data ingestion test program 💖

okay bestie, welcome to the <pink>file2sdr</pink> page, straight out of the ICI executables manual. it's a little test program, it's lowkey iconic, and we're gonna go through every single thing it does. no skips. no cap. 🫶

✨ SYNOPSIS ✨

file2sdr configFlags fileName

🌸 DESCRIPTION 🌸

so here's the vibe: file2sdr is a stress-test for SDR data ingestion. the way it does that is by repeatedly writing all the text lines of the file named fileName into one of a series of non-volatile linked lists, and those lists live inside a test SDR data store named <cyan>testsdr</cyan><cyan>configFlags</cyan> — like, the config flags get glued onto the end of the name, periodt.

and whyyy would you do that, you ask? because by folding the data store configuration into the name (for example <mint>testsdr14</mint>) it becomes relatively easy to run comparative testing on SDR data stores that are identical in every way except for their configuration settings. 💅 chefs kiss.

the whole operation is cyclical, okay? every time the program finishes copying the file's text lines it starts over, and a brand new linked list gets created for that new cycle. and here's the cute part: if you hit ^C to kill file2sdr and then restart it, it resumes operation at the point where it left off. it does not start over. it remembers. main character energy fr fr.

after writing each line to the current linked list, file2sdr gives a semaphore to signal that the list is now non-empty. this is mainly for the benefit of its complementary test program, sdr2file(1). 🦋

and at the end of each cycle? it appends a final EOF line to the current linked list containing exactly this text:

*** End of the file ***

and then it prints a brief performance report:

Processing I<lineCount> lines per second.

slay. that's the whole loop. 🔥

💀 EXIT STATUS 💀

  • "0" — file2sdr has terminated. that's it, that's the only one, bye. 👑

🎀 FILES 🎀

No configuration files are needed. not a single one. we're low maintenance like that. ✨

🧚 ENVIRONMENT 🧚

No environment variables apply. nothing to export, nothing to source, nothing to forget about. 🌈

🩺 DIAGNOSTICS 🩺

all the diagnostic messages that file2sdr produces get written to the ION log file <cyan>ion.log</cyan>. here's the full roster, no gatekeeping:

  • Can't use sdr. — ION system error. check for earlier diagnostic messages describing the cause of the error; correct problem and rerun.
  • Can't create semaphore. — ION system error. check for earlier diagnostic messages describing the cause of the error; correct problem and rerun.
  • SDR transaction failed. — ION system error. check for earlier diagnostic messages describing the cause of the error; correct problem and rerun.
  • Can't open input file — operating system error. check errtext, correct problem, and rerun.
  • Can't reopen input file — operating system error. check errtext, correct problem, and rerun.
  • Can't read from input file — operating system error. check errtext, correct problem, and rerun.
bestie if you see the ION ones, the move is always the same: go read the earlier messages in ion.log that explain what actually happened, fix it, rerun. don't just stare at it. 😭

🐛 BUGS 🐛

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

👀 SEE ALSO 👀

  • sdr2file(1) — the complementary test program, the other half of this duo 🫶
  • sdr(3)

and that's the page!! thank you for coming to my ted talk. this has been the FILE2SDR(1) page from the ICI executables manual, dated 2016-07-07, formatted by perl v5.24.1. mwah, go stress-test something responsibly. 💖✨🎀

📦 where this page comes from