Bug#531025: change in usage should be doc in NEWS. timeout command always take 'time' seconds to finish
javier.barroso at isotrol.com
Fri May 29 10:13:39 UTC 2009
Recently I noted about a different behaviour in one of my scripts.
timeout 1700 zenity --entry --text "What are you doing"
echo -e "Cat1\nCat2" | zenity --list --text "Category" --column "category"
Time before, second question was asked inmediately after first command was completed (after fill zenity question). Now with this newer timoeut I have to wait 1700 seconds ...
It would be great about have a option to terminate the program when command finish and not after time parameter seconds.
If this issue is the searched, please document it on NEWS or similar file.
~/empty$ timeout 10 ls
javi at pepinux:~/empty$ ps aux | grep timeout
javi 32111 0.0 0.0 1636 124 pts/3 S 12:12 0:00 timeout 10 ls
Thank you very much
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-1-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages timeout depends on:
ii libc6 2.9-13 GNU C Library: Shared libraries
timeout recommends no packages.
timeout suggests no packages.
-- no debconf information
More information about the forensics-devel