From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23566 invoked by alias); 10 Jul 2008 18:00:57 -0000 Received: (qmail 23187 invoked by uid 48); 10 Jul 2008 18:00:17 -0000 Date: Thu, 10 Jul 2008 18:00:00 -0000 Message-ID: <20080710180017.23186.qmail@sourceware.org> From: "fche at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20080404085514.6030.ananth@in.ibm.com> References: <20080404085514.6030.ananth@in.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/6030] stap, staprun, stapio interaction quirks: stale module left unloaded X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2008-q3/txt/msg00133.txt.bz2 ------- 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.