Hi,

Is there a canonical way to modify the stock Ubuntu systemd configuration so 
that it continues booting enough to bring up sshd after other service failures?

This is for remote servers, so the default failure mode of running an emergency 
shell on the console isn't useful.

What we have works most of the time when, for example, there is an fsck failure 
on a data disk, but it's not 100%.  When it doesn't work, there's a strange set 
of different orders of targets being reached, and some targets, like 
emergency.target being reached more than once.

Thanks, Jeff

Reply via email to