On 5/5/19 6:07 AM, Tom Horsley wrote:
But the service knows that. Why isn't there a way to tell systemd that in the .service file?
There's no use case for it. rngd is expected to terminate (more or less) immediately after it gets sigterm. If there were another directive to ignore shutdown status (as there is already a timeout setting), no one would have put that one in rngd's service file either.
systemd is doing what it was designed to do. It's operating correctly. Why is it more important to you to look for a reason to blame systemd than it is to simply correct the error in rngd? Does blaming systemd make a better community?
_______________________________________________ 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
