Here's an even simpler argument why random-seed-load and random-seed-save should be seen as two separate stateless services, not as the "start" and "stop" of some single long-lived service.
Suppose that during boot-up, random-seed-load fails for some reason. There are definitely ways this could happen. (OTOH there are a surprising number of things that could go wrong that systemd-random-seed save does /not/ report as an error ... but that is a topic for another day.) Now suppose that in the minutes, hours, or days that follow, the problem is resolved. Desired behavior: We really want the 'save' service to be performed at shutdown. The currently-observed behavior is that if 'load' failed then 'save' will never be performed. This is a Bad Thing from the security point of view. Splitting the services as discussed above makes this issue (among others) go away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652381 Title: systematic way to refresh the random-seed again and again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1652381/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
