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 ?
I believe you really want: sshd:12345:respawn:/usr/sbin/sshd -D
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 ?
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.
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.
Can you redirect the output from sshd in debug mode? Ie: sshd:23:respawn:/usr/local/sbin/sshd -ddd >/tmp/sshd-debug.log 2>&1 or whatever the correct syntax for Tru64 is?
3 months no reply == closed bug.