[BusyBox] init fails to start some applications

[Rob Landley]

On Monday 11 April 2005 10:52 am, Greg Waltz wrote:
> 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.

From the sshd man page:

   -D      When this option is specified, sshd will not detach and does not
             become a daemon.  This allows easy monitoring of sshd.

     -d      Debug mode.  The server sends verbose debug output to the system
             log, and does not put itself in the background.  The server also
             will not fork and will only process one connection.  This option
             is only intended for debugging for the server.  Multiple -d
             options increase the debugging level.  Maximum is 3.

     -e      When this option is specified, sshd will send the output to the
             standard error instead of the system log.

Me, I use dropbear:

http://matt.ucc.asn.au/dropbear/dropbear.html

Rob