please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1652381
Title:
Hi John,
We get the current random seed unit from systemd. Please file a bug with
the upstream systemd project, or discuss these changes on the systemd
mailing list.
Once your changes are accepted by systemd, we will inherit them.
Thanks!
** Changed in: systemd (Ubuntu)
Status: New =>
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
OK, I implemented approach (2) from the previous comment.
The work consists of six steps, in two groups of three:
++ create system/systemd-random-seed-load.service
++ create system/systemd-random-seed-save.service
-- get rid of the old system/systemd-random-seed.service
++ create
I retract patch and recipe mentioned in the initial report. The
problem is messier than I initially thought.
One fundamental consideration is that apparently systemctl won't
start a service that is marked active, and won't stop a service
that is marked inactive. This is inconsistent with
Wherever it goes, this part of the random-seed problems is not the
responsibility of the installer. Reassigning to systemd for now because
that's where systemd-random-seed.service lives.
** Package changed: ubiquity (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you
6 matches
Mail list logo
