This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded
- From: Ananth N Mavinakayanahalli <ananth at in dot ibm dot com>
- To: sourceware-bugzilla at sourceware dot org
- Cc: systemtap at sources dot redhat dot com
- Date: Fri, 4 Apr 2008 17:16:54 +0530
- Subject: [Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded
- References: <20080404085514.6030.ananth@in.ibm.com> <20080404111840.11550.qmail@sourceware.org>
- Reply-to: ananth at in dot ibm dot com
> 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.