On Sat, Jul 01, 2000 at 02:03:01PM -0700, Andrey A. Chernov wrote:
> On Sat, Jul 01, 2000 at 01:49:07PM -0700, Andrey A. Chernov wrote:
> > On Sat, Jul 01, 2000 at 07:00:07PM +0200, Mark Murray wrote:
> > > I've got this and some other tweaks commit-ready; I'll do them tomorrow...
> >
> > When running as cron job, from shell script, perl now always say this:
> > "Can't ignore signal CHLD, forcing to default" (see perl.c)
> >
> > 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?
OpenBSD already have simpler fix in rev 1.7 (below). I'll think which way is
better...
---------
Set SIGCHLD to SIG_DFL not SIG_IGN to prevent "perl -w" from
complaining "Can't ignore signal CHLD, forcing to default".
Setting SIGCHLD to SIG_IGN means "don't provide exit status for my
children" on some OSes which is not what we want--we just don't
want to catch SIGCHLD since our parent does that for us.
---------
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
