From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 105473 invoked by alias); 6 Jul 2016 20:15:20 -0000 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 Received: (qmail 105430 invoked by uid 89); 6 Jul 2016 20:15:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*Ad:U*jistone, whichever, H*f:sk:y0meg76, H*i:sk:577D648 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 06 Jul 2016 20:15:13 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 20226D4D88; Wed, 6 Jul 2016 20:15:12 +0000 (UTC) Received: from fche.csb (unused [10.10.52.236] (may be forged)) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u66KFB0T020105; Wed, 6 Jul 2016 16:15:11 -0400 Received: by fche.csb (Postfix, from userid 2569) id A2CDF5817C; Wed, 6 Jul 2016 16:15:14 -0400 (EDT) Date: Wed, 06 Jul 2016 20:15:00 -0000 From: "Frank Ch. Eigler" To: Alexander Lochmann Cc: Josh Stone , systemtap@sourceware.org Subject: Re: SystemTap for Android - patchset Message-ID: <20160706201514.GA29337@redhat.com> References: <56e0c7f4-d317-f76b-5156-3569a6097b62@tu-dortmund.de> <577CF9A2.7050008@tu-dortmund.de> <577D6483.9050507@tu-dortmund.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <577D6483.9050507@tu-dortmund.de> User-Agent: Mutt/1.4.2.2i X-SW-Source: 2016-q3/txt/msg00012.txt.bz2 Hi - On Wed, Jul 06, 2016 at 10:05:23PM +0200, Alexander Lochmann wrote: > [...] > > % sh pidwrapper /path/to/this.pid staprun foo bar baz > > > That would be a nice workaround. I went through the source code. The > commandline option is used by stapio. Stapio creates the pidfile. If I > send a SIGKILL (or was it a SIGTERM? what so ever) to staprun, stap and > the module won't be shutdown properly. Hence, I have to send the signal > to stapio. Since staprun exec's stapio, the latter will also share the same pid. So this wrapper would work, whichever process happens to be running at the moment. (Send SIGTERM or SIGINT for a clean shutdown.) - FChE