On 5/4/19 4:13 PM, Sam Varshavchik wrote:
In the good-old days, when integrating some new gizmo like rngd, by
the nature of the beast you'll always check into how it works and make
a minimal effort to learn its basics. Basic due diligence. From the
linked bugzilla bug, it seems that rngd was coded to ignore signals.
I don't think the conversation on that bug supports that conclusion.
This looks like it's simply a bug in rngd that causes an intermittent
failure to terminate. (If it intentionally ignored signals, the failure
would not be intermittent.)
We don't need tortured logic to blame systemd. It's doing the right
thing. There is a bug in rngd, and systemd is exposing that bug so that
it can be fixed. That's how software should work. "Errors should never
pass silently." (Zen of Python #10. Hello from Pycon!)