bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-28 Thread Bernhard Voelker
On 10/28/2015 11:00 AM, Pádraig Brady wrote: Reopened until someone else votes. I'm 50:50 regarding the usefulness of --verbose. Writing "killed PRG after N seconds elapsed" sounds like a useful message, yet I'm afraid that then other requests may follow soon which may really bloat the code,

bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-28 Thread Thomas Güttler
Am 26.10.2015 um 20:49 schrieb Pádraig Brady: > On 26/10/15 18:35, Thomas Güttler wrote: >> Am 26.10.2015 um 16:51 schrieb Pádraig Brady: >>> On 26/10/15 14:26, Thomas Güttler wrote: Am 26.10.2015 um 12:44 schrieb Pádraig Brady: > > I've not sure there is enough distinct

bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-28 Thread Pádraig Brady
reopen 21760 On 28/10/15 07:16, Thomas Güttler wrote: > Am 26.10.2015 um 20:49 schrieb Pádraig Brady: >> On 26/10/15 18:35, Thomas Güttler wrote: >>> Am 26.10.2015 um 16:51 schrieb Pádraig Brady: On 26/10/15 14:26, Thomas Güttler wrote: > > > Am 26.10.2015 um 12:44 schrieb

bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-28 Thread Bob Proulx
Bernhard Voelker wrote: > Pádraig Brady wrote: > >Reopened until someone else votes. > > I'm 50:50 regarding the usefulness of --verbose. > Writing "killed PRG after N seconds elapsed" sounds like a useful > message, yet I'm afraid that then other requests may follow soon > which may really bloat

bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-28 Thread Pádraig Brady
tag 21760 wontfix close 21760 stop Thanks for the additional input Jim, Bernhard and Bob.

bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-26 Thread Thomas Güttler
About commandline tool "timeout": Start COMMAND, and kill it if still running after DURATION. A new team mate wasted some time to debug why a process was killed with signal 15. I think it would be nice to have an --verbose option, and a some text which explains why the signal was send. This

bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-26 Thread Pádraig Brady
tag 21760 wontfix close 21760 stop On 26/10/15 10:30, Thomas Güttler wrote: > About commandline tool "timeout": Start COMMAND, and kill it if still running > after DURATION. > > A new team mate wasted some time to debug why > a process was killed with signal 15. > > I think it would be nice to

bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-26 Thread Thomas Güttler
Am 26.10.2015 um 16:51 schrieb Pádraig Brady: > On 26/10/15 14:26, Thomas Güttler wrote: >> >> >> Am 26.10.2015 um 12:44 schrieb Pádraig Brady: >>> >>> I've not sure there is enough distinct actions within timeout(1) to warrant >>> --verbose? >>> How about doing this in the script? >>> >>>

bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-26 Thread Pádraig Brady
On 26/10/15 14:26, Thomas Güttler wrote: > > > Am 26.10.2015 um 12:44 schrieb Pádraig Brady: >> >> I've not sure there is enough distinct actions within timeout(1) to warrant >> --verbose? >> How about doing this in the script? >> >>timeout 1s ping localhost >>test $? = 124 && echo {

bug#21760: timeout: Feature Request: --verbose ==> output if timeout was reached

2015-10-26 Thread Thomas Güttler
Am 26.10.2015 um 12:44 schrieb Pádraig Brady: I've not sure there is enough distinct actions within timeout(1) to warrant --verbose? How about doing this in the script? timeout 1s ping localhost test $? = 124 && echo { 'ping timed out'; exit 1; } The issue was already closed with