[SOLVED] Debian : Plymouth service disabled ( !) . How to update system to a safer mode ?

AngeloU · 01-24-2022, 01:36 AM

(Thanks everybody for help, also corrections concerning my english writing are well accepted).

Using Dmesg (after booting ) I found several errors in ''w h i t e ''

One error concerns service Systemd :

[ 5.393182] systemd[1]: /lib/systemd/system/plymouth-start.service:16:

(follows ----) :

Code:

.... Unit configured to use KillMode=none.
 This is unsafe, as it disables systemd's process lifecycle management for the service.
Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'.
 Support for KillMode=none is deprecated and will eventually be removed.

Two questions:

1. Is it necessary to update to Killmode= ?
2. If yes, how to update Systemd service ?

shruggy · 01-24-2022, 05:58 AM

As long as they are in white, they're warnings, not errors. And not very serious at that (priority NOTICE). Real errors are in red. Serious warnings are yellow.

I found this podman issue. One of the comments there says:

Quote:

There's nothing to worry about. systemd decided to gently deprecate KillMode=none as it was a continuous source of confusion and bugs.

Also see plymouth issue #123. Lennart Poettering himself commented there. A preliminary fix was committed to plymouth git about a year ago. It's already in Debian sid.

You may just copy /lib/systemd/system/plymouth-start.service to /etc/systemd/system and change it accordingly.

AngeloU · 01-31-2022, 03:01 AM

Many thanks for your answer, very helpful.

File below modified as suggested :

Quote:

/lib/systemd/system/plymouth-start.service *

[Unit]
Description=Show Plymouth Boot Screen
DefaultDependencies=no
Wants=systemd-ask-password-plymouth.path
After=systemd-udev-trigger.service systemd-udevd.service keyboard-setup.service
Before=systemd-ask-password-plymouth.service
ConditionKernelCommandLine=!plymouth.enable=0
ConditionKernelCommandLine=!nosplash
ConditionVirtualization=!container
IgnoreOnIsolate=true

[Service]
ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ExecStartPost=-/usr/bin/plymouth show-splash
Type=forking
RemainAfterExit=yes
KillMode=mixed
SendSIGKILL=no

Next step could be as follows ?

sudo cp /lib/systemd/system/plymouth-start.service /etc/systemd/system

Please confirm if said message is the right one to copy file to etc/systemd/system. (In order to avoid further errors).

shruggy · 01-31-2022, 03:32 AM

Wait. You should have first copied the unit file to /etc/systemd/system, and only then modified it. Don't change the files in /lib/systemd: they will be overwritten on the next systemd update.

The idea is you make a copy in /etc/systemd/system, and modify the copy. Anything in /etc/systemd/ will then override the accordingly named files in /lib/systemd/ and be used instead of them.