bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#77535: timeout treats very short durations as `0`


From: Philip Rowlands
Subject: bug#77535: timeout treats very short durations as `0`
Date: Sat, 05 Apr 2025 19:02:24 +0100

I was interested to see that the code makes uses of strtod, and how this 
interacts with the minute / hour / day suffix.

$ strace -e trace=clock_nanosleep sleep 3
clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=3, tv_nsec=0}, 

$ strace -e trace=clock_nanosleep sleep 0xas
clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=10, tv_nsec=0},

$ strace -e trace=clock_nanosleep sleep 0xam
clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=600, tv_nsec=0},

$ strace -e trace=clock_nanosleep sleep 0xad
clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=173, tv_nsec=0},

Here 0xad is interpreted as 173 seconds, not 10 days.

It's a corner case, but should sleep(1) support or tolerate hex input, and if 
so, how should it handle the "d" suffix? FWIW I'd just vote to return an error 
for hex intervals.


Cheers,
Phil





reply via email to

[Prev in Thread] Current Thread [Next in Thread]