[Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded

[Ananth N Mavinakayanahalli]

> We cannot reasonably recover from a kill -9 on staprun.  That is the only
> privileged process that can unload the module.  It may have been hand-started,
> leaving none of our code available to watch over it and restart it.  Teaching
> stap to re-fork staprun another time is perhaps possible, but in your
> "kill -9 stap staprun" scenario, that wouldn't help either.

Agreed. SIGKILL is a box case. SIGINT/SIGHUP can be handled though.

> Perhaps it's time to reconsider including a script such as
> http://sourceware.org/ml/systemtap/2008-q1/msg00051.html
> in the distribution.  Or a cron-driven systemtap module cleaner/unloader.

Yeah. That'd work too.