[Emacs-bug-tracker] bug#9100: closed (timeout should use setitimer if available)

[GNU bug Tracking System]

Your message dated Sat, 16 Jul 2011 12:25:59 -0700
with message-id <address@hidden>
and subject line Re: timeout should use setitimer if available
has caused the GNU bug report #9100,
regarding timeout should use setitimer if available
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
9100: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9100
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> timeout should use setitimer if available
>
>
>
>
> Date: 
>
> Sat, 16 Jul 2011 12:23:16 -0700
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; U; Linux i686; en-US;	rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
>
>
>
>
> 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 :-).
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: timeout should use setitimer if available
>
>
>
>
> Date: 
>
> Sat, 16 Jul 2011 12:25:59 -0700
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110617	Thunderbird/3.1.11
>
>
>
>
> Oops, sorry, sent that to the wrong bug address;
> it was meant for bug-coreutils.  Please ignore.
>
>
> --- End Message ---