openssh bugs - Sep 2003 - [Bug 716] OpenSSH 3.7.1p2: sshd doesn't start at reboot (Tru64 UNIX)

http://bugzilla.mindrot.org/show_bug.cgi?id=716

           Summary: OpenSSH 3.7.1p2: sshd doesn't start at reboot (Tru64
                    UNIX)
           Product: Portable OpenSSH
           Version: -current
          Platform: Alpha
        OS/Version: OSF/1
            Status: NEW
          Severity: major
          Priority: P2
         Component: sshd
        AssignedTo: openssh-bugs at mindrot.org
        ReportedBy: Ole.H.Nielsen at fysik.dtu.dk


The sshd daemon works correctly when started from the command line
under HP/Compaq Tru64 UNIX v4.0F (thanks to the fix in [Bug 653]).
The sshd is started at boot time from /etc/inittab like this:
   sshd::once:/usr/local/sbin/sshd
This used to work fine with OpenSSH 2.1.1p4.

Unfortunately, with the OpenSSH 3.7.1p2 sshd, no sshd process is
running after the reboot.  There are no error messages on the console,
nor in any syslog files.  When I login to the console and start
sshd from the command line, the daemon starts and works correctly.
Why won't sshd start from /etc/inittab ?  Is there an alternative
startup method for 3.7.1p2 ?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=716





------- Additional Comments From mouring at eviladmin.org  2003-09-26 01:02
-------
I believe you really want:

sshd:12345:respawn:/usr/sbin/sshd -D



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=716





------- Additional Comments From Ole.H.Nielsen at fysik.dtu.dk  2003-09-26 01:09
-------
I do not believe your syntax:
  > sshd:12345:respawn:/usr/sbin/sshd -D
to be valid on Tru64 UNIX.  Can you please explain why the -D flag
(do not become a daemon) would be a good idea ?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=716





------- Additional Comments From mouring at eviladmin.org  2003-09-26 02:03
-------
Deamonizing needs to be disabled otherwise it confuses init.  It no longer 
knows how to manage the process.

And if this is not the right syntax for Tru64 then Tru64 is broken because 
inittab is an extremely old concept (pre-OSF).

If you do a search on "inittab sshd -D" on google you'll see
multiple documents
talking about this.  Multiple commentary on it.  Even if you just look back 
through the openssh-unix-dev@ list you'll see it is the correct solution.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=716





------- Additional Comments From Ole.H.Nielsen at fysik.dtu.dk  2003-09-29 22:09
-------
Following Ben Lindstrom I changed by /etc/inittab to read:
   sshd:23:respawn:/usr/local/sbin/sshd -D

When rebooting (or doing "init q") I get these error messages
on the console:

   INIT: Command is respawning too rapidly. Check for possible errors.
   id:  sshd "/usr/local/sbin/sshd -D"

So with or without the -D flag, sshd version 3.7.1p2 doesn't seem
to be startable from /etc/inittab on Tru64 UNIX.  Version 3.6 of
sshd didn't have these problems.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.