[BusyBox] init fails to start some applications

[Greg Waltz]

sshd is getting run. It gets loaded and is visible from the ps right 
afterwards, but it exits shortly thereafter.

The return value of the last program is 0, but that is probably not from 
sshd as it is still running at that time (unless the first process 
initiated by the shell exits and it's a child that is shown below...).

  PID  Uid     VmSize Stat Command
    1 root        536 S   init
*snip*
  109 root       1536 R   /usr/sbin/sshd -e
  111 root        648 R   ps ax

I am still stuck on this issue. We will probably end up continuing to 
use 0.52 and just add the non-BusyBox versions of the extra applications 
that we need.


Rob Landley wrote:

>On Thursday 24 March 2005 01:52 pm, Greg Waltz wrote:
>
>  
>
>>I am launching inetd from a script called by init (for telnetd). inetd
>>runs most of the time with the 1.00 init. inetd is getting run after
>>sshd, so I tried switching the order, putting inetd before sshd in
>>inittab. Now, sshd runs most of the time and inetd fails.
>>
>>Could there be a problem with forking that goes away after the first
>>failure?
>>    
>>
>
>Could be any number of things.
>
>What I'd do is look at your script that fires off init, and right after sshd 
>gets run I'd add:
>
>echo $? > /out.txt
>ps ax >> /out.txt
>
>That might tell you if sshd is not being run at all (perhaps not being found 
>due to a path issue or something), or if it's being fired off but exiting 
>immediately...
>
>Rob
>
>  
>


-- 
Greg Waltz