From: Stephen Frost <sfrost@snowman.net>
To: bert hubert <ahu@ds9a.nl>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: jiffies rollover, uptime etc.
Date: Mon, 18 Feb 2002 19:58:13 -0500 [thread overview]
Message-ID: <20020218195813.O20319@ns> (raw)
In-Reply-To: <3C717DEA.7090309@candelatech.com> <E16cwUx-00073d-00@the-village.bc.nu> <20020219002614.A27210@outpost.ds9a.nl>
In-Reply-To: <20020219002614.A27210@outpost.ds9a.nl>; from ahu@ds9a.nl on Tue, Feb 19, 2002 at 12:26:14AM +0100
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
* bert hubert (ahu@ds9a.nl) wrote:
> $ uname -a ; uptime
> Linux newyork-1 2.2.18 #3 Mon Dec 11 15:57:33 EST 2000 i686 unknown
> 6:22pm up 425 days, 1:35, 3 users, load average: 0.10, 0.05, 0.01
Linux ns2 2.2.16 #1 Sun Jul 30 21:57:38 EDT 2000 i386 unknown
19:55:29 up 1 day, 15:06, 1 user, load average: 0.00, 0.03, 0.00
-rw-r--r-- 1 root root 1569 Oct 8 2000 /var/log/dmesg
No problems here so far, just wrapped. Processes seemed to all handle
it okay though ps now shows some things started in 2003.. :)
> This server is pretty remote and hard to reach, and not sure to reboot
> properly unattended - are there predictions about how well 2.2.18 will
> survive jiffy wraparound?
It's honestly not good to not know how to reboot a box unattended. :)
> Would you consider it worth rebooting for? By the way, this is our second
> most important production server, I'm exceedingly pleased with the
> stability. We've abused it no end.
I'd certainly make arrangements to have it rebooted if necessary. If
rebooting is a huge problem then I'd say just have someone on hand in
case you *have* to.
Stephen
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-02-19 0:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 21:42 jiffies rollover, uptime etc Oliver Hillmann
2002-02-18 22:10 ` Alan Cox
2002-02-18 22:03 ` Oliver Hillmann
2002-02-18 22:19 ` Ben Greear
2002-02-18 22:32 ` Tim Schmielau
2002-02-18 22:43 ` Alan Cox
2002-02-18 23:26 ` bert hubert
2002-02-18 23:56 ` J Sloan
2002-02-18 23:57 ` Alan Cox
2002-02-19 0:58 ` Stephen Frost [this message]
2002-02-19 4:47 ` Paul Jakma
2002-02-19 0:17 ` Bill Davidsen
2002-02-19 20:55 ` george anzinger
2002-02-20 11:36 ` Ville Herva
2002-02-20 17:20 ` Mike Fedyk
2002-02-20 17:24 ` Rik van Riel
2002-02-20 17:32 ` Mike Fedyk
2002-02-20 17:39 ` Rik van Riel
2002-02-20 17:44 ` Mike Fedyk
2002-02-20 17:56 ` Derek Gladding
2002-02-21 13:19 ` Bill Davidsen
2002-02-20 19:08 ` David Mosberger
2002-02-20 19:53 ` Robert Love
2002-02-20 15:46 ` Bill Davidsen
2002-02-20 16:50 ` george anzinger
2002-02-18 22:12 ` Tim Schmielau
2002-02-18 23:22 ` J Sloan
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 2:54 Chris Adams
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=20020218195813.O20319@ns \
--to=sfrost@snowman.net \
--cc=ahu@ds9a.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--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