Re: SIGCONT misbehaviour in Linux
H. Peter Anvin (hpa@transmeta.com)
8 Dec 1999 12:22:20 -0800
Followup to: <19991208100219.A18129@stormix.com>
By author: Simon Kirby <sim@stormix.com>
In newsgroup: linux.dev.kernel
> >
> > and the process running sleep 1000 immediatly returns on Linux. I tested it
> > on other systems and it works correctly (the sleep continue).
>
> Hmm...This works properly on libc5 systems, btw. (glibc2.0 and glibc2.1
> use nanosleep(), libc5 uses alarm() and sigsuspend()).
>
It really could be argued what is the right behaviour here. When a
system call is interrupted by the signal, the normal thing is to
return EINTR.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/