I created Bug 1774788 which is for rsyncd not starting at boot and was
provided with a fix by Andreas Hasenack that works. I tried using that
fix for ssh and it does not work.

Both services fail when an attempt is made to specify a particular NIC
via their respective config files. In the case of rsync, the fix was to
create the override.conf file containing:

[Unit]
After=network.target,network-online.target

via the command systemctl edit rsync.service

Using a similar procedure to create the override.conf file for ssh does
not fix the ssh daemon startup issue. I'm curious as to why that is.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549473

Title:
  ssh will not start at boot:  systemctl status ssh -> output is listed
  as failed 255.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1549473/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to