Re: [linuxsh-dev] waitpid and 2.4.0 kernel

[Denis D. <ddo...@po...>]

Hi Brian,

I have attached the init patch for busybox. I am still using
busybox-0.47 but I suspect this patch will work with newer versions of
busybox. This patch makes init set the SIGCHLD handling to SIG_DFL. This
should not be needed but for some reason the 2.4.0 kernel is starting
the init process with SIGCHLD set to SIG_IGN.

Regards,
Denis.

PS: If you have the flash space I would replace busybox sh with a real
version of bash. It makes the target environment SO much more user
friendly.


Bryan Rittmeyer wrote:
> 
> Denis Dowling wrote:
> 
> > The seems to be a 2.4.0 SH kernel problem but I could not find a way to fix
> > this. Instead I set SIG_CHLD to SIG_DFL in the busybox init program I am
> > using and all works correctly.
> 
> Could you please supply me a patch for this?
> 
> > I suspect that this is fixed in the latest BusyBox release and broken in
> > 0.48. Strange though?
> 
> Actually, I am still seeing this problem with 0.49pre BusyBox CVS and
> 2.4.0-pre2 LinuxSH CVS. For example:
> 
> [@(none) /]# mount -t ramfs ramfs mnt
> mount: Mounting ramfs on mnt failed: No such device
> sh: tcsetpgrp: Operation not permitted
> sh: waitpid(56): No child processes
> Process '/bin/busybox sh' (pid 11) exited.  Scheduling it for restart.
> 
> Please press Enter to activate this console.
> 
> I don't think the "tcsetpgrp" complaint is related, but I did start
> seeing it after moving up from 2.4.0-test10. Perhaps I need to upgrade
> to glibc2.2?