A quick update to close on my (rejected) foray into an equivalent solution for systemd-standalone-tmpfiles (#1139903):
On Fri, Jun 12, 2026 at 08:54:26AM +0100, Andrew Bower wrote: > On Wed, Jun 10, 2026 at 01:27:12AM +0200, Lorenzo wrote: > > I'm attaching an updated version of the patches where > > stop actions are turned into no-op > > I attach initscripts I am using with systemd-standalone-tmpfiles which I > would like to refine. Following your lead I also dropped the 'stop' > action, although I am wondering if I should include the '0 6' stop > runlevels anyway, at the expense of shutdown log noise, because just > filling out the stop stub later is a lot easier than also changing the > configured runlevels on existing installations? I opted to include the stop runlevels (like Lorenzo's seedfiles version) for the reason I stated above - ease of adding to later if needed. > In this version, 'TYPE=oneshot' gives us a meaningful 'status' query at > the expense of needing to use 'restart' instead of 'start' to reapply > the operation. > > One question for Mark in relation to init-d-script(5) is that by using > DAEMON=none, as required for this type of service, we lose the automatic > "this package is still installed" check - what is the idiomatic way to > reinstate that - would it be a 'start_pre' override to test for it? The answer is, just specify a value for DAEMON= as long as stop, start and status are all overriden (or defined by the TYPE=oneshot implementation) then it will do the right thing. > Should we also put drop-ins to /etc/insserv.conf.d of the form: > > $x-tmpfiles: seedfiles No colon here. > So that we can add an LSB dependency for scripts in packages which have > decided to rely on tmpfiles for essential content? I decided this probably wasn't needed because runlevels 2-5 are already sequenced after this and the scripts in runlevel S tend not to rely on tmpfiles so it seemed over the top.
