FUNCTION::EXIT(3stap)

πŸ’– NAME πŸ’–

function::exit β€” bestie, this is how you start shutting down your probing script. like, initiating the goodbye. the beginning of the end, if you will ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

exit()

πŸŽ€ ARGUMENTS πŸŽ€

None πŸ’… β€” she takes nothing. zero. nada. no arguments, no notes, no baggage.


🌸 DESCRIPTION 🌸

okay so here's the tea, and it's important tea: exit() does not slam the door shut immediately. it only enqueues a request to start shutting down the script. it's giving "hey can we wrap this up" energy, not "everybody out NOW" energy.

what that means in practice, fr fr:

  • New probes will not fire β€” except end probes πŸ‘‘ (those still get to do their thing, iconic behaviour honestly)
  • But every probe that's currently running? they may complete their work. no cutting anyone off mid-sentence. let them finish, they're doing great 🫢

so like, it's a polite shutdown request sitting in the queue. not an instant kill. don't expect the script to be gone the millisecond you call it. lowkey the most considerate function in the whole tapset ngl πŸ’œ

not me writing a whole paragraph about a function with no arguments 😭 but the semantics MATTER bestie, exit() is not kill(), iykyk

⭐ SEE ALSO ⭐

  • tapset::logging(3stap) β€” go read this one too, it's the whole logging family, they're all connected 🧚

and that's the whole page!! slay πŸ’…

this lil gem lives in the SystemTap Tapset Reference, under the Logging Tapset section, and this particular copy is dated September 2026 🌈 (the version field is just chillin' there as Ver, short and mysterious, we respect that πŸ™ˆ). anyway, exit() when you're done, bestie, and may all your end probes run flawlessly πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from