From: Willy Tarreau <willy@w.ods.org>
To: Nick Warne <nick@linicks.net>
Cc: Rumi Szabolcs <rumi_ml@rtfm.hu>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.x kernel uptime counter problem
Date: Thu, 19 Jan 2006 21:27:34 +0100 [thread overview]
Message-ID: <20060119202734.GR7142@w.ods.org> (raw)
In-Reply-To: <200601192022.42087.nick@linicks.net>
On Thu, Jan 19, 2006 at 08:22:42PM +0000, Nick Warne wrote:
> On Thursday 19 January 2006 20:18, Willy Tarreau wrote:
>
> > > You can use:
> > > last -xf /var/run/utmp runlevel
> > >
> > > to get true uptime in this instance.
> > >
> > > Nick
> >
> > I would add that if you need to get valid outputs after such an uptime,
> > you can apply the vhz-j64 patch available at Robert Love's (RML) on
> > kernel.org.
>
> :-( Then you would have to start all over again and wait 497.1 days to see if
> it works... :-0
No, you can apply the debugjiffies patch which basically sets your time
to -5 min at boot to test the wrapping. Anyway, believe me, it works, I
successfully wrapped twice on 2.4.18 a long time ago, and it was not
that clean by this time.
> Seriously, is this patch to be added to 2.4.x tree at all in the future?
No, because it uses dirty (but very clever) tricks to avoid locking around
the jiffies manipulations, and 2.4 is in critical fixes-only mode right now.
> Nick
Regards,
Willy
next prev parent reply other threads:[~2006-01-19 20: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 [this message]
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
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=20060119202734.GR7142@w.ods.org \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
--cc=rumi_ml@rtfm.hu \
/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