From: Paul Faure <paul@engsoc.org>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.0.35 limits
Date: Sat, 16 Jun 2001 01:27:10 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0106160114340.439-100000@stout.engsoc.carleton.ca> (raw)
In-Reply-To: <E15B17v-000790-00@the-village.bc.nu>
The exact uptime is unknown, so it may have actually been 497 days.
No matter, since we will now upgrade the system. We held back on the
upgrade before since it had such a nice uptime. Better than any other
system on campus and its run by student volunteers.
Thanks for the info.
On Fri, 15 Jun 2001, Alan Cox wrote:
> > Just this morning, our firewall get a kernel panic after 500 days of
> > uptime.
>
> Interesting very interesting in fact. There is a 497 day wrap on the kernel but
> it should do nothing more than send the uptime back to zero. I'm not sure
> how the crash fits in to this but it could be significant that its about
> the wrap time
>
--
Paul N. Faure 613.266.3286
Chief Technical Officer, CertainKey Inc. paul@certainkey.com
Carleton University Systems Eng. 3rd Year paul@faure.ca
Engineering Society Administrator paul@engsoc.org
next prev parent reply other threads:[~2001-06-16 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 19:54 drivers/usb/ov511.c does not compile Kelledin Tane
2001-06-15 20:05 ` Johannes Erdfelt
2001-06-15 20:34 ` Alan Cox
2001-06-15 20:52 ` Johannes Erdfelt
2001-06-15 21:23 ` Kernel 2.0.35 limits Paul Faure
2001-06-15 21:27 ` Alan Cox
2001-06-16 5:27 ` Paul Faure [this message]
2001-06-16 12:11 ` Thomas Bogendoerfer
2001-06-15 21:35 ` Alexander Viro
2001-06-15 20:11 ` drivers/usb/ov511.c does not compile Kelledin Tane
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=Pine.LNX.4.33.0106160114340.439-100000@stout.engsoc.carleton.ca \
--to=paul@engsoc.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).