Date: Sun, 02 Jul 2000 09:39:39 +0200 From: Mark Murray <mark@grondar.za> To: "Andrey A. Chernov" <ache@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: perl, cron or sh bug Message-ID: <200007020739.JAA20526@grimreaper.grondar.za> In-Reply-To: <20000701140301.A32165@freebsd.org> ; from "Andrey A. Chernov" <ache@FreeBSD.ORG> "Sat, 01 Jul 2000 14:03:01 MST." References: <20000701140301.A32165@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007020739.JAA20526>