From: fche@redhat.com (Frank Ch. Eigler)
To: Mike Mason <mmlnx@us.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: Fwd: Any way to find the network usage by a process?
Date: Fri, 06 Oct 2006 15:30:00 -0000 [thread overview]
Message-ID: <y0mu02hsbqr.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <4525AD02.10301@us.ibm.com>
Mike Mason <mmlnx@us.ibm.com> writes:
> [...]
> >> The only way to avoid the error is use @sum only if @count > 0,
> >> which makes the printf too complex in my opinion.
> [...]
Actually, another way is to add a "<<< 0" dummy value to the
stats arrays in a new "probe begin", then to display @count()-1
and @sum() etc.
- FChE
next prev parent reply other threads:[~2006-10-06 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3420082f0610030114o5b44b8ak7797483e02002614@mail.gmail.com>
[not found] ` <3420082f0610030114o4c6998en907bccce81d28c59@mail.gmail.com>
2006-10-03 15:49 ` Jose R. Santos
2006-10-04 20:54 ` Mike Mason
2006-10-05 21:22 ` Frank Ch. Eigler
2006-10-05 23:28 ` Mike Mason
2006-10-06 0:00 ` Frank Ch. Eigler
2006-10-06 1:10 ` Mike Mason
2006-10-06 15:30 ` Frank Ch. Eigler [this message]
2006-10-06 1:08 Stone, Joshua I
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=y0mu02hsbqr.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=mmlnx@us.ibm.com \
--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).