From owner-freebsd-current Sun Jul 2 7:28:54 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 4038337BCD7; Sun, 2 Jul 2000 07:28:52 -0700 (PDT) Date: Sun, 2 Jul 2000 07:28:52 -0700 From: "Andrey A. Chernov" To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: perl, cron or sh bug Message-ID: <20000702072852.B43640@freebsd.org> References: <20000701140301.A32165@freebsd.org> <200007020739.JAA20526@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200007020739.JAA20526@grimreaper.grondar.za>; from mark@grondar.za on Sun, Jul 02, 2000 at 09:39:39AM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 02, 2000 at 09:39:39AM +0200, Mark Murray wrote: > > > 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... I already solve this thing. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message