On Samstag, 30. November 2024 15:19:28 Mitteleuropäische Normalzeit Andrei Borzenkov wrote:
30.11.2024 16:55, mh@mike.franken.de wrote:
Hi *,
because of the recent problems with plymouth I checked my journal for plymouth messages more thoroughly and found:
Nov 30 14:29:51 client systemd[1]: plymouth-switch-root.service: Deactivated successfully. Nov 30 14:29:52 client systemd[1]: plymouth-start.service: Found left- over process 463 (plymouthd) in control group while starting unit. Ignoring. Nov 30 14:29:52 client systemd[1]: plymouth-start.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Is that an expected behavior?
SUSE sets KillMode=none for plymouth-start.service which means any process will not be terminated by systemd when (if) unit stops. So yes, it is sort of expected.
OK. There is also a journal entry telling me, that KillMode=none is deprecated, so this should be changed sometimes in the future, I guess.
OTOH I do not see it on any of my VM.
Nov 30 17:00:09 tw systemd[1]: Starting Show Plymouth Boot Screen... Nov 30 17:00:10 tw systemd[1]: Started Show Plymouth Boot Screen. Nov 30 17:00:42 tw systemd[1]: Starting Terminate Plymouth Boot Screen... Nov 30 17:00:47 tw systemd[1]: Finished Terminate Plymouth Boot Screen.
It is started in initrd and actually never stopped by systemd. GDM terminates plymouthd on its own. The "Terminate Plymouth Boot Screen" is plymouth-quit.service which in this case runs because I booted into run level 3.
In your case the message is likely due to "systemctl daemon-reload".
Jepp.
It seems, that the plymouth process from the early boot phase remained running - correct?
This is actually the very idea of plymouth - it is supposed to show splash screen from the earliest possible moment without interruption.
Yes, that was clear to me, but not why systemd complains about a still running process. But your explanation helped a lot, thx! Bye. Michael.