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);
>
> > 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
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 ru
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 igno
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 cro
