systemd vs. upgrades
- To: Michael Cree <cree@waikato.ac.nz>
- Cc: debian-alpha@lists.debian.org
- Subject: systemd vs. upgrades
- From: Bob Tracy <rct@gherkin.frus.com>
- Date: Tue, 3 Nov 2015 06:50:11 -0600
- Message-id: <[🔎] 20151103125011.GA14189@gherkin.frus.com>
- In-reply-to: <20151103053721.GA13242@gherkin.frus.com>
- References: <20151101223533.GA3453@gherkin.frus.com> <20151101225617.GA3591@gherkin.frus.com> <20151101231134.GC13468@cree.waikato.ac.nz> <20151102145952.GA10967@gherkin.frus.com> <20151102195731.GA26499@cree.waikato.ac.nz> <20151103000435.GA11714@gherkin.frus.com> <20151103002756.GA12175@gherkin.frus.com> <20151103035813.GA12951@gherkin.frus.com> <20151103041634.GH26499@cree.waikato.ac.nz> <20151103053721.GA13242@gherkin.frus.com>
Unrelated to the specific upgrade issues, there's a larger problem with
Debian since the switch to "systemd". Namely, if any upgrade touches
something controlled by "systemd", the odds of being able to do a clean
shutdown/reboot drop to approximately zero: the shutdown process hangs
due to services which became "unregistered" to allow for their replacement,
and you then have to hit the reset switch.
This is in no way a good thing. My disks have been scanned by fsck far
more often than would otherwise be necessary over the past several months.
I suppose I should be grateful that the resulting mess seems to be
getting cleaned up reliably -- thus far. If userspace doesn't get
touched between reboots, there's no issue: kernel upgrades in recent
times cause no more "excitement" than they traditionally have :-).
--Bob
Reply to: