Date: Sat, 1 Jul 2000 14:03:01 -0700 From: "Andrey A. Chernov" <ache@freebsd.org> To: Mark Murray <mark@grondar.za> Cc: current@freebsd.org Subject: Re: perl, cron or sh bug Message-ID: <20000701140301.A32165@freebsd.org> In-Reply-To: <20000701134907.A29454@freebsd.org>; from ache@freebsd.org on Sat, Jul 01, 2000 at 01:49:07PM -0700 References: <20000701204443.A43672@nagual.pp.ru> <200007011700.TAA17595@grimreaper.grondar.za> <20000701134907.A29454@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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? -- Andrey A. Chernov <ache@nagual.pp.ru> http://ache.pp.ru/ 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?20000701140301.A32165>