On Tue, Mar 1, 2011 at 10:58 AM, Andrey Borzenkov <arvidj...@gmail.com> wrote: > 1) plymouth-quit is not ever started. I do not understand why - it is > queued, and it should be started after rc-local.service is finished > and it is not. Log attached. >
Forget this. I had plymouth-quit with local modification in this VM. Sorry for the noise. The rest is still valid though :) > 2) getty's now are ordered after plymouth-quit-wait, so they are never > started until plymouth --wait finishes. But it never finishes because > plymouth-quit is never run. Unfortunately, TimeoutSec is not applied > to oneshot units so it just sits there forever. Patch attached. After > booting with it I see that plymouth-quit is actually run but apprently > *after* plymouthquit-wait which has failed. > > [root@localhost ~]# systemctl status plymouth-quit.service > plymouth-quit.service - Terminate Plymouth Boot Screen > Loaded: loaded (/etc/systemd/system/plymouth-quit.service) > Active: inactive (dead) since Thu, 03 Mar 2011 17:16:32 > -0500; 2min 41s ago > Process: 1448 ExecStart=/bin/plymouth quit (code=exited, > status=0/SUCCESS) > CGroup: name=systemd:/system/plymouth-quit.service > [root@localhost ~]# systemctl status plymouth-quit-wait.service > plymouth-quit-wait.service - Wait for Plymouth Boot Screen to Quit > Loaded: loaded (/lib/systemd/system/plymouth-quit-wait.service) > Active: failed since Thu, 03 Mar 2011 17:16:31 -0500; 2min 44s ago > Main PID: 917 > CGroup: name=systemd:/system/plymouth-quit-wait.service > > Offhand: it would be *really* nice to have here explanation *why* > service failed. You cannot expect people searching for this in logs > every time, really. > > systemd[1]: plymouth-quit-wait.service operation timed out. Terminating. > _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
