Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> writes: > Using systemd-sysusers and systemd-tmpfiles more widely was mentioned a > few times, along with a statement that an implementation for non-systemd > systems would need to be provided. Both those programs work just fine > without systemd not running as PID1. (systemd has unit files to start > them automatically during boot and at regular intervals, so that part > would need to be reimplemented appropriately for a given init system if > desired. The programs themselves don't care at all how they are > started.)
Hi Zbigniew, Do you know if systemd upstream would be willing to commit to that continuing to be the case? I wasn't sure if that would be an acceptable limitation; if not, that's certainly an easy solution for those two facilities. I admit that I can't think of any reason why they wouldn't run without systemd as PID 1, but I wasn't sure I was anticipating possible future changes. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
