GNU bug report logs - #9102
"timeout 0 FOO" should timeout right away

Previous Next

Package: coreutils;

Reported by: Paul Eggert <eggert <at> cs.ucla.edu>

Date: Sat, 16 Jul 2011 19:35:01 UTC

Severity: normal

Full log


Message #11 received at 9102 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Alan Curry <pacman-cu <at> kosh.dhis.org>
Cc: 9102 <at> debbugs.gnu.org
Subject: Re: bug#9102: "timeout 0 FOO" should timeout right away
Date: Sat, 16 Jul 2011 15:27:55 -0700
On 07/16/11 15:08, Alan Curry wrote:
> What's the difference between running a command with a 0 second timeout
> and not running the command at all? It could be killed before it even gets
> scheduled.

Yes, exactly.  "timeout 0 FOO" should be the limit case for

timeout 1 FOO
timeout 0.1 FOO
timeout 0.01 FOO
timeout 0.001 FOO

That is, its behavior shouldn't diverge markedly from that of
"timeout 1e-300 FOO".




This bug report was last modified 13 years and 336 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.