From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Willy Tarreau <willy@w.ods.org>
Cc: Jim Paris <jim@jtan.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: time() glitch on 2.4.18: solved
Date: 05 Nov 2002 18:16:31 +0000 [thread overview]
Message-ID: <1036520191.5012.109.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20021105171035.GB879@alpha.home.local>
On Tue, 2002-11-05 at 17:10, Willy Tarreau wrote:
> On Tue, Nov 05, 2002 at 11:30:20AM -0500, Jim Paris wrote:
> > + if (count > LATCH) {
>
> may be (count >= LATCH) would be even better ?
Some PIT clones seem to hold the LATCH value momentarily judging by
other things that were triggered wrongly by >=
next prev parent reply other threads:[~2002-11-05 17:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 6:37 time() glitch on 2.4.18 at 177 days uptime? Jim Paris
2002-11-03 19:32 ` time() glitch on 2.4.18: solved Jim Paris
2002-11-03 20:30 ` Alan Cox
2002-11-05 16:30 ` [PATCH] " Jim Paris
2002-11-05 16:54 ` george anzinger
2002-11-05 17:10 ` Willy Tarreau
2002-11-05 18:16 ` Alan Cox [this message]
2002-11-05 18:02 ` Jim Paris
2002-11-05 18:37 ` Alan Cox
2002-11-05 18:20 ` Willy Tarreau
2002-11-05 18:50 ` Jim Paris
2002-11-05 17:14 ` Willy Tarreau
2002-11-05 17:42 ` Jim Paris
2002-11-05 18:57 ` Richard B. Johnson
2002-11-05 19:08 ` Willy Tarreau
2002-11-05 19:29 ` Richard B. Johnson
2002-11-05 20:07 ` Alan Cox
2002-11-05 20:14 ` Willy Tarreau
2002-11-05 20:38 ` Richard B. Johnson
2002-11-05 23:15 ` Willy Tarreau
2002-11-06 12:47 ` Richard B. Johnson
2002-11-06 13:25 ` Alan Cox
2002-11-06 23:21 ` Jim Paris
2002-11-05 20:23 ` Richard B. Johnson
2002-11-05 20:57 ` Alan Cox
2002-11-05 20:41 ` Richard B. Johnson
2002-11-06 15:09 ` Christer Weinigel
2002-11-06 15:49 ` Richard B. Johnson
2002-11-05 20:06 ` Alan Cox
2002-11-05 17:32 ` Alan Cox
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=1036520191.5012.109.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jim@jtan.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®