[systemd-devel] [PATCH] Try to start rescue.target if default.target is missing

[Lennart Poettering]

On Tue, 11.09.12 12:06, Tomasz Torcz (tomek at pipebreaker.pl) wrote:

> >From 0a3f3b2a46607a94efd2936ae7094a9ef7421e76 Mon Sep 17 00:00:00 2001
> From: Tomasz Torcz <tomek at pipebreaker.pl>
> Date: Fri, 7 Sep 2012 14:14:44 +0200
> Subject: [PATCH] Try to start rescue.target if default.target is missing
> 
> In rare cases when default.target symlink is missing, systemd fails
> instantly and gets into reboot loop.
> Noticed by XReaper on IRC.
> Be a bit more resilient, try to fallback to rescue.target first.

Hmm, so we actually ship a symlink
/usr/lib/systemd/system/default.target → graphical.target by default
these days. That means that if the user has no such link in /etc we'll
still be able to boot just fine.

This makes me wonder how the "default.target" symlink can be
missing?

That all said we acually have precisely this logic already in place,
i.e. if you look further down when we are actually trying to load the
unit.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.