This is the mail archive of the
mailing list for the glibc project.
Re: The relative timeout in linuxthreads
- From: "H . J . Lu" <hjl at lucon dot org>
- To: Marcus Brinkmann <Marcus dot Brinkmann at ruhr-uni-bochum dot de>
- Cc: GNU C Library <libc-alpha at sources dot redhat dot com>
- Date: Wed, 6 Feb 2002 15:56:36 -0800
- Subject: Re: The relative timeout in linuxthreads
- References: <20020206152641.A31597@lucon.org> <20020206234647.GE1587@22.214.171.124>
On Thu, Feb 07, 2002 at 12:46:47AM +0100, Marcus Brinkmann wrote:
> You were not very specific about the exact situation you want to fix, and
> what guarantees you want to make, but the above is what I read from the
> standard about absolute and relative time outs.
Suppose the machine starts with
Thu Feb 6 20:34:00 PST 2020
and a thread wants to wait for 30 seconds. Then the machine notices
the clock is way off. The clock is set with
# rdate -s clockserver
Wed Feb 6 15:42:35 PST 2002
Since pthread waits in the absolute time, that pthread won't time out
until 2020 :-).