linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James <james@piku.org.uk>
To: linux-admin@vger.kernel.org
Subject: Re: utmp rollover at 496 days?
Date: Thu, 9 May 2002 20:33:51 +0100	[thread overview]
Message-ID: <20020509193351.GL7173@piku.org.uk> (raw)
In-Reply-To: <5.1.0.14.0.20020509105827.00b139e0@mustang>

On Thu, May 09, 2002 at 11:09:05AM -0700, Scott Taylor wrote:
| At 10:53 AM 09/05/2002, you wrote:
| 
| >I have two machines which have not been rebooted sind Dec 2000.
| 
| Way to go.

Indeed! And I thought 200 days was good :)

| >At day 497, on both machines, the uptime command began anew at day 0.
| 
| Don't you think it's time for a good cleaning and maybe replace a hard 
| drive or two by now?

Nah, if it still works, leave it be. Although it has rolled over, so it
doesn't look as "eleet" when you type "uptime" any more...
 
| >Anybody know what's up with that?
| 
| Guessing Linus didn't figure you would run it so long, with out some kind 
| of maintenance, so using a very short integer to count days would save 
| space in the kernel.  I've only seen this question asked about 3 times, and 
| once was for an SCO UNIX (maybe XENIX) that would crash on day 498.

There's another way to track uptime now. It requires a very technical
tool known as a "black marker". Every time the counter rolls, make a
mark on the computer's casing :-)

-- 
This punishment is not boring and pointless  
 
6AD6 865A BF6E 76BB 1FC2 | www.piku.org.uk/public-key.asc
E4C4 DEEA 7D08 D511 E149 | www.piku.org.uk wnzrf@cvxh.bet.hx (rot13'd)

  reply	other threads:[~2002-05-09 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09 17:53 utmp rollover at 496 days? jim roy
2002-05-09 18:09 ` Scott Taylor
2002-05-09 19:33   ` James [this message]
2002-05-09 18:15 ` Joseph Bueno

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=20020509193351.GL7173@piku.org.uk \
    --to=james@piku.org.uk \
    --cc=linux-admin@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).