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: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 10 Jul 2008 18:00:17 -0000
- Subject: [Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded
- References: <20080404085514.6030.ananth@in.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2008-07-10 18:00 -------
> There is a second part to this problem, in that i'm having to kill the stap
> process twice from my program to exit.
This should only occur if the first signal didn't get through to the whole
process group. If stapio received the first signal, it should shut down in
a timely manner, and let stap shut down cleanly too within a few seconds.
The second signal should only be necessary if something broke with handling the
first one - it's sort of a user-level patience timeout measure that should not be
necessary for mechanical use.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6030
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.