On 5/4/19 9:32 AM, Sam Varshavchik wrote:
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.
As usual, it is not a systemd problem, unless you consider that trying
to do a clean shutdown is brain damage. The rngd process gets stuck
sometimes (see the above mentioned bug) and systemd waits nicely for it
to stop, but finally gives up and force kills it.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
