What stops plymouthd late in boot with systemd?
dsd at laptop.org
Sat Mar 17 10:48:18 PDT 2012
We're working with adopting OLPC's boot animation for plymouth on F17
and making good progress.
A question: during a boot with systemd, what is the process/mechanism
used to make plymouthd quit just before starting X?
It's not plymouth-quit.service because, grepping for "plymouth-quit"
of a log of a standard boot:
[ 11.193037] systemd: Looking at job plymouth-quit.service/stop
[ 11.200714] systemd: Looking at job plymouth-quit.service/start
[ 11.208377] systemd: Fixing conflicting jobs by deleting job
[ 11.772106] systemd: Installed new job
plymouth-quit-wait.service/start as 92
[ 48.260388] systemd: plymouth-quit-wait.service changed dead -> start
[ 50.832695] systemd: Child 500 belongs to plymouth-quit-wait.service
[ 50.856148] systemd: plymouth-quit-wait.service: main process
exited, code=exited, status=0
[ 50.882849] systemd: plymouth-quit-wait.service changed start -> dead
[ 50.905421] systemd: Job plymouth-quit-wait.service/start
[ 51.135402] systemd: plymouth-quit-wait.service: cgroup is empty
(i.e. plymouth-quit.service is never executed)
The context is that I'm trying to run a script (to completion)
immediately *before* the plymouth daemon is terminated, and I'm not
sure where I can hook this in.
More information about the plymouth