Thanks for reporting that problem. It is fixed in the latest test release. ftp://alpha.gnu.org/gnu/fetish/sh-utils-2.0a.tar.gz Raul Miller <[EMAIL PROTECTED]> writes: | Sleep terminates abnormally if you stop it and restart it. | | However, it acts as if this is normal behavior. | | It should sleep for the proper time. [Or, failing that, I suppose I | might be able to live with an error exit for the case where it terminates | abnormally soon.] | | My preferred implementation would check time before going to sleep, | and if the return code is -EINTR to go back to sleep for an appropriate | length of time. | | Here's the tail end of a "time strace sleep 100000" session where I hit | control-z then fg: | | rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0 | rt_sigaction(SIGCHLD, NULL, {SIG_DFL}, 8) = 0 | rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 | nanosleep({100000, 0}, | [1]+ Stopped strace sleep 100000 | | real 0m6.953s | user 0m0.000s | sys 0m0.000s | $ fg | strace sleep 100000 | 0xbffffa28) = -1 EINTR (Interrupted system call) | _exit(0) = ? | $ | | I ran into this when trying to demonstrate job control to a class of | students. Needless to say, some of them were unhappy..
