From: fche@redhat.com (Frank Ch. Eigler)
To: "Sébastien Dugué" <sebastien.dugue@bull.net>
Cc: systemtap <systemtap@sources.redhat.com>,
Pierre PEIFFER <pierre.peiffer@bull.net>
Subject: Re: _stp_pid no longer there?
Date: Wed, 28 Mar 2007 14:20:00 -0000 [thread overview]
Message-ID: <y0mabxxmouk.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <20070328120810.37633ce8@frecb000686.frec.bull.fr>
SÚbastien DuguÚ <sebastien.dugue@bull.net> writes:
> I just discovered that the _stp_pid module parameter has just
> vanished from runtime/transport/transport.c.
Yes, it seems to have gone away with the recent rewrite of the area.
This might have been because
> What is supposed to replace it or how one is supposed to retreive
> staprun's pid from within a script as it is used by tapsets?
Using variables defined by runtime C code directly is not appropriate.
Such code is considered to be a private interface between the
translator, the provided tapsets, and the runtime, and thus may change
frequently.
However, I agree that it is sometimes desirable to filter out events
caused caused by staprun's activities, so a properly documented and
tapset-exported version of that pid number should come back.
- FChE
next prev parent reply other threads:[~2007-03-28 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 10:11 Sébastien Dugué
2007-03-28 10:26 ` Andreas Kostyrka
2007-03-28 10:51 ` Sébastien Dugué
2007-03-28 14:20 ` Frank Ch. Eigler [this message]
2007-03-28 15:34 ` Sébastien Dugué
2007-03-28 17:23 ` Frank Ch. Eigler
2007-03-28 14:48 ` Martin Hunt
2007-03-28 15:40 ` Sébastien Dugué
2007-03-28 16:13 ` Martin Hunt
2007-03-29 6:50 ` Sébastien Dugué
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=y0mabxxmouk.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=pierre.peiffer@bull.net \
--cc=sebastien.dugue@bull.net \
--cc=systemtap@sources.redhat.com \
/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).