On Mon, 2014-11-03 at 23:18 +0200, Mert Dirik wrote: > Anyway, best approach seems to be listening the recommendation of > systemd maintainers instead of inventing our own methods. In the bug > I've linked in the previous message: > > > On Mon, 03 Nov 2014 14:19:07 +0100 Michael Biebl <bi...@debian.org> wrote: > >> > >> The systemd system runtime directory is only created when systemd is the > >> active PID 1. Could you elaborate why you think this approach is > >> fragile? If those two tests (for systemd and upstart) would be brittle, > >> we'd have a problem, since they are used all over the place. > >> > > I didn't tested it but I can't see any reason why it shouldn't work. > > Thanks for your time and involvement.
Something changed with systemd recently. My test system that was last updated Oct 10 continues to work fine with kexec-tools 2.0.7-3 while the test system I updated this morning no longer works (it used to). Any way, I am working on a solution based upon /run/systemd. Hopefully this will be a reliable solution. -- Khalid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
