This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Is it ok to insert a module multiple times with staprun?
- From: Arkady <arkady dot miasnikov at gmail dot com>
- To: Shiyao Ma <i at introo dot me>
- Cc: systemtap at sourceware dot org
- Date: Thu, 30 Mar 2017 08:40:02 +0300
- Subject: Re: Is it ok to insert a module multiple times with staprun?
- Authentication-results: sourceware.org; auth=none
- References: <CAJQX3DyhKKCn6U+T4oBcMs6NHHo1zQwsD2fASjnytiTdGKYz5w@mail.gmail.com>
Linux kernel krpobes farmework supports multiple probes for the same function.
On Thu, Mar 30, 2017 at 7:41 AM, Shiyao Ma <i@introo.me> wrote:
> Hi,
> In the staprun manpage, I saw this:
>
>
> -R Rename the module to a unique name before inserting it.
>
> So looks like it's safe to insert it multiple times as long as the -R
> gives a different name.
>
>
> My application scenario is to log information on different tcp
> connections, and separately output them to different files.
> The invocation is like this:
> # first insertion
> sudo staprun /path/to/module -o /path/to/tcp-2003 filterport=2003 -R tcp-2003
> # second insertion
> sudo staprun /path/to/module -o /path/to/tcp-2004 filterport=2004 -R tcp-2004
>
> Does the above approach look natural?
>
> Regards.