No sshd as of the latest update

[D. R. Evans]

D. R. Evans wrote on 05/20/2015 01:30 PM:
> 
> I have created the /var/run/sshd directory manually, and now /usr/bin/sshd
> executes when started manually; I'll try to boot the machine when it's not
> needed and see if sshd now starts properly at boot time as well.
> 

All users were off the machine so I rebooted it...

... but "reboot" doesn't work any more. It eventually enters a state where
everything is dead and the power needs to be removed and reapplied manually.

"reboot -f", though, *does* work. I note that the man page says of the "-f"
option:

      -f, --force
           Force immediate halt, power-off, reboot. Do not contact the init
system.

So it seems that something in the init system is responsible for the failure
of "reboot" to... reboot.

But it gets worse :-(

Having manually created /var/run/sshd so that sshd could run, I have now
discovered that the directory no longer exists at the time of the next boot
(whe I reboot using "reboot -f". So at the next boot, sshd again fails to start.

So the upshot is that I have a remote system that seems to have no way to
start sshd at boot time.

<tangent>
I have watched the debate about systemd for the past year or so, thinking
(perhaps too smugly) that by the time came that users were exposed to it, it
would be at least reasonably usable. I have now been forced to revise that hope.
</tangent>

It would a whole lot easier to find a solution and get this working without
resorting to installing a different distro, though. Reasonable suggestions as
to how to proceed are welcome and invited.

  Doc

-- 
Web:  http://www.sff.net/people/N7DR

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/kubuntu-users/attachments/20150520/9522802c/attachment.sig>