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


View this message in rfc822 format

From: "Alan Curry" <pacman-cu <at> kosh.dhis.org>
To: eggert <at> cs.ucla.edu (Paul Eggert)
Cc: 9102 <at> debbugs.gnu.org
Subject: bug#9102: "timeout 0 FOO" should timeout right away
Date: Sat, 16 Jul 2011 17:08:44 -0500 (GMT+5)
Paul Eggert writes:
> 
> "sleep 0" sleeps for zero seconds, and "timeout 0 FOO"
> should timeout in zero seconds as well.  Currently,
> it doesn't; it times out in an infinite number of seconds.
> I see why, from the internals (alarm (0) is a special
> call intended to cancel alarms).  However, 'timeout' shouldn't
> be exposing those internals to users; it should behave like
> 'sleep' does, as that's more consistent.
> 

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.

-- 
Alan Curry




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.