Messages in this thread | | | Subject | Re: Possible task exit bug? | From | Andreas Schwab <> | Date | 25 May 1999 11:02:54 +0200 |
| |
Jonathan Larmour <jlarmour@cygnus.co.uk> writes:
|> If I run this directly from the shell, its fine - there's no output. If I |> run it from a cron or "at" job on Linux I get "error: No child processes" |> i.e. ECHILD. This works on Solaris but fails on both linux 2.0.36/glibc2.0 |> and linux 2.2.2/glibc2.1. But its not clear to me why it succeeds on a tty, |> but not from cron. I get the same effect on a tty if I put an explicit |> "signal(SIGCHLD, SIG_IGN);" near the top.
Have you tried putting "signal(SIGCHLD, SIG_DFL)" near the top?
-- Andreas Schwab "And now for something schwab@issan.cs.uni-dortmund.de completely different" schwab@gnu.org
- 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/
| |