Tom Horsley writes:
I'm frequently rebooting my new fedora 30 install as I test things, and on one reboot I got the entire boot process held up by a stop job for rngd.service. I'm rebooting for God's sake. Why do you need to stop the reboot process to wait till you've gathered enough entropy which will be thrown away immediately on reboot? Can a individual service file be configured to exit immediately on reboot?
There's a default 90 second timeout on stopping a service, before it gets forcefully stopped.
Maybe 1 in every 20 if my reboots gets held up for "stopping user processes".Apparently, I am asked to believe that selecting "Reboot" from the desktop does not always stop every user process, for some reason, even though X is completely killed, as well as everything that should be started from it, or from the user login.
I just wait 90 seconds, in those instances, and write it off as yet another systemd brain damage.
According to systemd.service man page, TimeoutStopSec sets this timeout. So you can add that to rngd.service, I suppose. Or, if you want to bring out the big hammer, set DefaultTimeoutStopSec in /etc/systemd/system.conf, effectively changing the default timeout for everything.
How can you possibly get stopping a piddly daemon, like rngd, wrong? Who knows. It's brain damage.
Attachment:
pgpzkk76NN5E0.pgp
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
