> > I am not shure, is this cron bug calling with ignoring SIGCHLD, sh bug, or
> > perl bug. I think cron shouldn't call anything with SIGCHLD ignored.
> Yes, it was in cron/do_command.c
> (void) signal(SIGCHLD, SIG_IGN);
> What about re-allowing SIGCHLD after second fork (i.e.vfork), just before
> execle()? Any objections?
Not from me, as long as the implications are understood...
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message