RTABORT(nged)

terminate all active raytrace subprocess(es)

πŸ“… published 7.44.0, from nixpkgs unstable

πŸ’… RTABORT(nged) β€” the nged manual, bestie edition

okay so picture this: you're in nged (that's BRL-CAD's user command manual, iykyk) and you've got raytraces running wild. This page is your "stop everything" button. Let's get into it πŸŽ€


✨ NAME ✨

rtabort β€” terminate all active raytrace subprocess(es). yes, ALL of them. no cap. πŸ’€


✨ SYNOPSIS ✨

rtabort

that's it. that's the whole vibe. no flags, no arguments, nothing to memorize πŸ¦‹


✨ DESCRIPTION ✨

The rtabort command terminates any currently running raytrace subprocesses launched from the current MGED session. literally the cleanup queen πŸ‘‘

This includes processes started by rt, rtwizard, art, and rtcheck. all of them get the invite to leave. 🫢

The command takes no arguments. Here's the tea on how it works: it scans the list of active subprocesses, identifies those whose executable name matches one of the raytrace programs, and sends a termination signal to each one. Every process is also marked as aborted in the session state. iconic behavior, honestly.

If no raytrace subprocesses are currently running, rtabort returns without error. no drama, no error message, just a peaceful "nothing to do here" 🌸

πŸ“Œ Note: rtabort only affects raytrace subprocesses started in the current session. It does not affect rt processes started from a separate shell or another MGED session. so like… stay in your lane, bestie β€” this command only cleans up your mess πŸ’…

✨ EXAMPLES ✨

Example 1. Abort an active raytrace

mged> rt -o output.png scene.g assembly.c mged> rtabort

Launches an rt raytrace in the background, then immediately terminates it with rtabort. it's giving "started a project and abandoned it in the same breath" 😭 honestly relatable ✨


✨ SEE ALSO ✨

  • rt(nged)
  • rtwizard(nged)
  • rtcheck(nged)

go read those too, they're the supporting cast πŸ¦‹


✨ AUTHOR ✨

BRL-CAD Team β€” the main characters of this whole story πŸ‘‘


✨ BUG REPORTS ✨

Reports of bugs or problems should be submitted via electronic mail to devs@brlcad.org. found a problem? tell the devs, don't suffer in silence, bestie πŸ’–


and that's the whole page!! πŸŽ€βœ¨

cute little sign-off: this lil masterpiece is part of BRL-CAD and lives in the RTABORT(nged) manual page β€” version/date vibes as printed by the manpage, and we are obsessed. periodt. πŸ§šπŸ’œ

πŸ“¦ where this page comes from