Skip to content

fetch-crl-boot service config should include RemainAfterExit=yes (bugzilla bug #48)

Michel Jouvin 2018-09-17 18:15:41 CEST

Hi,

fetch-crl-boot service can take some time to complete and with the current configuration of the systemd unit (EL7), every time systemctl start fetch-crl-boot is entered, the service is run again (as opposed to systemctl restart). This is due to the fact that the unit configuration doesn't include 'RemainAfterExit=yes'.

IMO, this is an unexpected behaviour. After the boot, the service should remained in the so called 'active (exited)' state and the sysadmin should use the restart command to reexecute it if needed.

This problem has a minor impact, as long as you don't use a management system (Quattor in our case) that redo the start command for every service declared (intentionally) to be on in the configuration. With every service, except fetch-crl-boot, this has the effect of doing nothing if the service already runs.

Michel

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information