From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] stats.c bug
Date: Wed, 18 Jun 2003 16:59:34 -0400 [thread overview]
Message-ID: <f088f20c4819214cd8158c5a124fa6af@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306181420040.31535-100000@fbsd.cpsc.ucalgary.ca>
> if a machine is left running cpu-heavy applications for a long time (say,
> a week) those numbers will overflow and strtol() will return LONG_MAX as the
> value. the net effect is that stats.c will not display context, syscalls and
> interrupts properly.
umm, what if i leave it running for two weeks?
next prev parent reply other threads:[~2003-06-18 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 20:51 andrey mirtchovski
2003-06-18 20:59 ` Russ Cox [this message]
2003-06-18 21:57 ` andrey mirtchovski
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=f088f20c4819214cd8158c5a124fa6af@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).