public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Alexander Lochmann <alexander.lochmann@tu-dortmund.de>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Josh Stone <jistone@redhat.com>, systemtap@sourceware.org
Subject: Re: SystemTap for Android - patchset
Date: Wed, 06 Jul 2016 20:05:00 -0000	[thread overview]
Message-ID: <577D6483.9050507@tu-dortmund.de> (raw)
In-Reply-To: <y0meg7690rn.fsf@fche.csb>


[-- Attachment #1.1: Type: text/plain, Size: 1725 bytes --]

On 06.07.2016 18:42, Frank Ch. Eigler wrote:
> Alexander Lochmann <alexander.lochmann@tu-dortmund.de> writes:
> 
>> [...]
>> I chose the letters randomly. For me, it doesn't matter. I just need an
>> argument to tell staprun to create a pid file. :)
> 
> Would it be enough for staprun to have that pid option?
> That would mean the stap script would have to be compiled
> through to -p4 only, then staprun invoked manually.
> 
Yes, that should do.
>> Yeah, sure. Since I run stap on Android, I have a background service,
>> which periodically checks if every single stap instance is still
>> running. Yes, it might be possible having more than one stap script
>> running. :) [...]
> 
> Since your background service is already custom, maybe a custom shell
> script wrapper like this could serve your purposes without having to
> change staprun/stap at all:
> 
> % cat pidwrapper
> #! /bin/sh
> pidfile="$1"; shift
> program="$1"; shift
> echo $$ > $pidfile
> exec $program ${1+$@}  # exec to preserve $$ pid
> 
> and then you invoke staprun via:
> 
> % 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.

- Alex
> - FChE
> 


-- 
Technische Universität Dortmund
Alexander Lochmann                PGP key: 0xBC3EF6FD
Otto-Hahn-Str. 16                 phone:  +49.231.7556141
D-44227 Dortmund                  fax:    +49.231.7556116
http://ess.cs.tu-dortmund.de/Staff/al


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-06 20:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f01a1f27-3cdb-61a4-cbdb-7bffd1032c8e@tu-dortmund.de>
2016-07-01 16:15 ` Alexander Lochmann
2016-07-01 16:56   ` David Smith
2016-07-01 17:47   ` Josh Stone
2016-07-06 12:29     ` Alexander Lochmann
2016-07-06 16:42       ` Frank Ch. Eigler
2016-07-06 20:05         ` Alexander Lochmann [this message]
2016-07-06 20:15           ` Frank Ch. Eigler
2016-07-06 20:27             ` Alexander Lochmann
2016-07-07 16:00       ` David Smith
2016-07-07 16:06       ` David Smith
2016-07-07 16:23         ` Alexander Lochmann
2016-07-07 17:39           ` David Smith
2016-07-07 20:51             ` Alexander Lochmann
2016-07-07 21:14               ` David Smith
2016-07-08  5:38                 ` Alexander Lochmann
2016-07-08 15:31                   ` David Smith
2016-07-07 18:47       ` David Smith
2016-07-07 19:01         ` Alexander Lochmann
2016-07-07 19:24           ` David Smith
2016-07-07 19:32             ` Alexander Lochmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=577D6483.9050507@tu-dortmund.de \
    --to=alexander.lochmann@tu-dortmund.de \
    --cc=fche@redhat.com \
    --cc=jistone@redhat.com \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).