From owner-freebsd-current Sun Jul 2 0:39:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 4A9F437B65D; Sun, 2 Jul 2000 00:39:03 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id JAA20526; Sun, 2 Jul 2000 09:39:40 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200007020739.JAA20526@grimreaper.grondar.za> To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: perl, cron or sh bug References: <20000701140301.A32165@freebsd.org> In-Reply-To: <20000701140301.A32165@freebsd.org> ; from "Andrey A. Chernov" "Sat, 01 Jul 2000 14:03:01 MST." Date: Sun, 02 Jul 2000 09:39:39 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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