public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Willy Tarreau <willy@w.ods.org>, Rumi Szabolcs <rumi_ml@rtfm.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.x kernel uptime counter problem
Date: Sat, 21 Jan 2006 08:35:17 -0500	[thread overview]
Message-ID: <43D23895.7080801@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0601201731130.10065@yvahk01.tjqt.qr>

Jan Engelhardt wrote:

>>>Or use some dedicated programs, IIRC there is a "uprecords" program
>>>(http://podgorny.cz/moin/Uptimed). Does require no reboot and should work
>>>right away.
>>>      
>>>
>>I never understood uptime anyway, the boot time, to the second, is available in
>>/proc/stat (btime), and it isn't that hard to turn it into whatever format you
>>find human readable. I have a perl script which presents uptime as fractional
>>days, days, hours, min, sec, and/or boot time. Took me about two minutes to
>>write.
>>    
>>
>
>uptime or uptimed/uprecords? (That's two different things.)
>The "uptime" commands is the same as "w | head -n1" (which reads 
>/proc/uptime) and therefore suffers from jiffies wrap.
>

I understand why it has this limitation, the question is why it was 
written to have it, when correct function is easily possible. I 
understand extra effort to get it right, but not to get it wrong...

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


      reply	other threads:[~2006-01-21 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 10:08 2.4.x kernel uptime counter problem Rumi Szabolcs
2006-01-19  9:29 ` Nick
2006-01-19 20:18   ` Willy Tarreau
2006-01-19 20:22     ` Nick Warne
2006-01-19 20:27       ` Willy Tarreau
2006-01-20 14:15       ` Jan Engelhardt
2006-01-20 15:18         ` Bill Davidsen
2006-01-20 16:32           ` Jan Engelhardt
2006-01-21 13:35             ` Bill Davidsen [this message]

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=43D23895.7080801@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rumi_ml@rtfm.hu \
    --cc=willy@w.ods.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