fiu-run(1)

📦 version 1.2, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing

💖 fiu-run(1) 💖

General Commands Manual · the libfiu launcher script, bestie edition

✨ NAME ✨

fiu-run — a script to launch programs using libfiu 🎀

🌸 SYNOPSIS 🌸

fiu-run [options] program [program arguments]

🦋 DESCRIPTION 🦋

okay so fiu-run is a script, right, and its whole thing is making it so much easier to launch programs with libfiu(3). Like, it can enable failure points AND spin up libfiu's remote control capabilities before it even starts executing the program — which means you don't have to go write some special launcher just to inject failures. the way that saves you an entire side quest… 💅

it's especially iconic when you're injecting failures into the POSIX/libc functions, because it does not require any program modifications. none. zero. your code stays untouched, no cap. ✨

and after you've launched programs with fiu-run, you can use fiu-ctrl(1) to enable and disable their failure points at runtime. live. mid-run. main character energy fr fr. 👑

for additional documentation, go to the project's website at http://blitiri.com.ar/p/libfiu 🌈

🎀 OPTIONS 🎀

  • -c command — run the given libfiu remote control command before executing the program (see below for reference, bestie, it's right there 🫶)
  • -x — use the POSIX libfiu preload library; this allows you to simulate failures in the POSIX and C standard library functions 💀✨
  • -f ctrlpath — enable remote control over named pipes with the given path as base name; the process id will be appended. it defaults to "$TMPDIR/fiu-ctrl", or "/tmp/fiu-ctrl" if "$TMPDIR" is not set. set it to "" to disable remote control over named pipes entirely 🙈
  • -l path — path where to find the libfiu preload libraries. defaults to the path where they were installed, so it is usually correct, no stress 🌸

🌟 Remote control commands 🌟

remote control commands are of the form "command param1=value1,param2=value2". valid commands are:

  • 'enable name=NAME' — enables the NAME failure point unconditionally. no take-backs, it's just on 🔥
  • 'enable_random name=NAME,probability=P' — enables the NAME failure point with a probability of P. chaos, but make it a percentage 🎲

all of the enable* commands can also optionally take failnum and failinfo parameters, analogous to the ones taken by the C functions. iykyk 🧚

🌈 EXAMPLES 🌈

the following will run the fortune(1) program simulating faults in read() with 5% probability (note that the -x parameter is required in this case to enable failure points in the POSIX and libc functions):

fiu-run -x -c "enable_random name=posix/io/rw/read,probability=0.05" fortune

by running it multiple times you will see that sometimes it works, but most of the time you get different errors, resulting from the simulated failures. literally a different vibe every single time you run it 😭🍓

👑 SEE ALSO 👑

libfiu(3), fiu-ctrl(1).

💀 BUGS 💀

if you want to report bugs, or have any questions or comments, just let me know at albertito@blitiri.com.ar. for more information about libfiu, you can go to http://blitiri.com.ar/p/libfiu. bestie i am begging you, please tell me about the bugs 🙏✨

and that's the whole page, slay! 💖✨ this little gem comes from fiu-run(1), dated 16/Jun/2009 — a certified classic, honestly, ate and left no crumbs 🎀🦋⭐
📦 where this page comes from