[BusyBox] init fails to start some applications

[Jason Schoon]

I have attached my patch that fixed up my system.

Again, this should not be considered a fix.  Rather it is a temporary
workaround that restored expected behavior to my product.  When I (or
someone else) have time, a correct fix should be created.


On Thu, 24 Mar 2005 11:50:04 -0500, Greg Waltz <gwaltz at catalystcorp.com> wrote:
> Jason,
> Thanks for the info. I tried merging the 1.00 init.c with 1.00-pre10,
> but it still had the same problem. I also tried building from the pre1
> tree and the current snapshot with the same results. I considered going
> back as far as 0.60.5, but the configuration file is probably a lot
> different at that point.
> 
> Any other ideas?
> 
> btw, below is the minor change that I had to make to the pre10 init.c to
> get it to build in 1.00:
> diff busybox-1.00-pre10/init/init.c busybox-1.00/init/init.c
> 232c232,234
> <               syslog_msg(LOG_DAEMON, LOG_INFO, msg + 1);
> ---
>  >               openlog(bb_applet_name, 0, LOG_DAEMON);
>  >               syslog(LOG_INFO, "%s", msg);
>  >               closelog();
> 
> Thanks
> 
> 
> Jason Schoon wrote:
> 
> >Greg,
> >
> >I have seen this as well.  I think it occurred with the init change
> >right before the 1.00 release to allow for reloading inittab.  I
> >haven't had the time to investigate the correct solution yet, but for
> >now I was able to revert init.c to a version from 1.00-pre10 (what I
> >happened to have at the moment) and it worked correctly again.
> >
> >Just haven't had the time to revisit it yet.
> >
> >
> >On Wed, 23 Mar 2005 15:45:32 -0500, Greg Waltz <gwaltz at catalystcorp.com > wrote:
> >
> >
> >>I am using busybox 1.00 with glibc 2.2.1. I had been using busybox 0.52
> >>for quite some time without problems.
> >>However, I needed some of the applications that were added in later
> >>versions, so I built and tried the latest version.
> >>
> >>I am running sshd from a script that is called by init from a line in
> >>/etc/inittab. This scheme has worked rather well for nearly a year, but
> >>now it is failing with the new busybox. The script gets run, but sshd is
> >>not running afterwards. Switching back to 0.52 fixes the problem.
> >>I thought that it might be an issue with the busybox shell, but I have
> >>been using a stand-alone bash with the exact same symptoms.
> >>
> >>I am loading telnetd via a method similar to the sshd script. It had
> >>been working with 1.00 at first, but it just started failing like the
> >>sshd script today.
> >>
> >>Running either script from the shell works without trouble.
> >>
> >>I have not seen any bug reports like this one and I am not sure where to
> >>look for more information.
> >>
> >>Thanks
> >>
> >>--
> >>Greg Waltz
> >>
> >>
> >>_______________________________________________
> >>busybox mailing list
> >>busybox at mail.busybox.net 
> >>http://busybox.net/mailman/listinfo/busybox
> >>
> >>
> >>
> >>
> >>
> >_______________________________________________
> >busybox mailing list
> >busybox at mail.busybox.net 
> >http://busybox.net/mailman/listinfo/busybox
> >
> >
> >
> 
> --
> Greg Waltz
> 
> _______________________________________________
> busybox mailing list
> busybox at mail.busybox.net 
> http://busybox.net/mailman/listinfo/busybox
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: busybox-init.patch
Type: application/octet-stream
Size: 2490 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/busybox/attachments/20050324/51f7de95/attachment.obj