[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#9101: timeout should use setitimer if available
From: |
Pádraig Brady |
Subject: |
bug#9101: timeout should use setitimer if available |
Date: |
Mon, 18 Jul 2011 11:01:06 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 |
On 16/07/11 20:28, Paul Eggert wrote:
> setitimer has nanosecond resolution, which is better than the
> one-second resolution that 'alarm' has. timeout should use
> setitimer if available, to take advantage of this. On 64-bit
> hosts, this has the additional advantage of increasing the
> upper bound for timeouts from 2**31 seconds to 2**63 seconds
> (about 68 years to about 292 billion years, which should be
> long enough for most practical purposes :-).
I'll apply this soon.
cheers,
Pádraig.
timeout-float.diff
Description: Text Data
- bug#9101: timeout should use setitimer if available, Paul Eggert, 2011/07/16
- bug#9101: timeout should use setitimer if available, Jim Meyering, 2011/07/17
- bug#9101: timeout should use setitimer if available,
Pádraig Brady <=
- bug#9101: timeout should use setitimer if available, Paul Eggert, 2011/07/18
- bug#9101: timeout should use setitimer if available, Pádraig Brady, 2011/07/18
- bug#9101: timeout should use setitimer if available, Paul Eggert, 2011/07/18
- bug#9101: timeout should use setitimer if available, Pádraig Brady, 2011/07/19
- bug#9101: timeout should use setitimer if available, Paul Eggert, 2011/07/19
- bug#9101: timeout should use setitimer if available, Pádraig Brady, 2011/07/19
- bug#9101: timeout should use setitimer if available, Paul Eggert, 2011/07/19
- bug#9101: timeout should use setitimer if available, SciFi, 2011/07/19