mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $?
0
mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $?
0
mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $?
124
mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $?
124
mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $?
0
mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $?
124
This is pretty much certainly not a coreutils issue, but I haven't
figured out what package to assign it to yet. Anyone seen anything like
it? Basically, calling timer_settime repeatedly with the same value
yields different outcomes. This is causing build test failures for
coreutils on kFreeBSD, and I'm not sure it's something I should force
through by suppressing the test. Sometimes when this happens there's a
really long delay before the program returns. I've tried various test
values, and it doesn't require the time be exactly MAX_INT to faile
(smaller values fail also).
The prior version of timeout didn't use setitimer, and one fix would be
to ignore that function when building on kFreeBSD, but that would mean
the program would have different features depending on which Debian
platform it's running on.