Hi! On Sun, Sep 05, 1999 at 11:47:22PM +0200, Guido Flohr wrote: > Try to run a time consuming task like "find /usr/ >/dev/null 2>&1". > Hit CTRL-Z, will you get a prompt? Mhmm, if it's really SIGSTOP that isn't handled correctly, then pressing ^Z won't test it, as this sends SIGTSTP, which - in opposite to SIGSTOP, /can/ be caught, while SIGSTOP (as SIGKILL) can neither be caught, nor ignored, nor handled. So, what should bash handle with SIGSTOP, anyway? For job control, using the correct parameters to wait3() or waitpid() is cruical to correctly detect stopped children. Ciao Thomas -- Thomas Binder (Gryf @ IRCNet) gryf@hrzpub.tu-darmstadt.de PGP-key available on request! binder@rbg.informatik.tu-darmstadt.de Vote against SPAM: http://www.politik-digital.de/spam/
Attachment:
pgpGxghZ_pqIV.pgp
Description: PGP signature