Bug#991185: systemd: 'systemctl start anacron.service' from emergency mode kills emergency shell

Zack Weinberg zackw at panix.com
Wed Jul 21 21:11:55 BST 2021


On Wed, Jul 21, 2021 at 9:46 AM Michael Biebl <biebl at debian.org> wrote:
> When emergency mode is triggered (either by a boot failure or adding
> emergency to the kernel command line), emergency.target is started and
> emergency.service as a result of it.
>
> sysinit.target has "Conflicts=emergency.service emergency.target"
...

Thanks for the explanation.

> Would you be willing to file an upstream bug report?
> Maybe there is a way, to find a solution for this without causing a
> regression.

I see that you reopened https://github.com/systemd/systemd/issues/6509
so I commented there instead of filing a brand new report.

> For the time being, you might consider using single/rescue mode. It
> doesn't seem to have such a conflicts with sysinit.target.

I'll keep that in mind, thanks.  I suppose I can always *stop* the
handful of services started by rescue.target if they're interfering
with repairs, instead of avoiding starting them in the first place.

zw



More information about the Pkg-systemd-maintainers mailing list