On Wed, Sep 12, 2012 at 03:17:18PM -0700, Kok, Auke-jan H wrote: > On Wed, Sep 12, 2012 at 3:15 PM, Kok, Auke-jan H > <auke-jan.h....@intel.com> wrote: > > On Tue, Sep 11, 2012 at 3:06 AM, Tomasz Torcz <to...@pipebreaker.pl> wrote: > >> From 0a3f3b2a46607a94efd2936ae7094a9ef7421e76 Mon Sep 17 00:00:00 2001 > >> From: Tomasz Torcz <to...@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. > >> + > >> + if (arg_running_as == MANAGER_USER) > >> + goto finish; > >> + else { > > ignore that, I just reread your patch and that's what you're actually > doing here, it seems, for the user session, or does it error out for > the user session here?
I had not worked yet with user sessions, the patch was for systemd running as PID1. default.target may go missing for couple of reasons - disk corruption, overzealous admin, honest mistake. Yet Lennart pointed that systemd should cope with that situation, I had to ask XReaper why in his situation it didn't. -- Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML) _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel