On Thu 18/Apr/2019 12:41:57 +0200 Tom H wrote: >>> I've always assumed that: >>> >>> - the rcX.d links are only meant to be changed by running "insserv" >>> (directly or via update-rc.d) >>> >>> - the dependencies of "/etc/init.d/foo" should be changed via >>> "/etc/insserv/overrides/foo" >> >> That sounds overly procrustean if applied rigorously, don't you think so? > > On a personal laptop, maybe. > > In a professional context, with multiple sysadmins and systems, > definitely not. The insserv man page should really say something like > "the /etc/rcX.d directories are owned by insserv and the symlinks that > they contain should not be edited manually."
What's the point of having manually editable links, then? Create a binary file containing the boot recipe, à la systemd, and you can be almost sure that your ban against manual interventions is duly respected. > If creating "/etc/insserv/overrides/foo" is too much, there's always > the option of editing "/etc/init.d/foo" directly, since it's generally > (always?) a dpkg conffile. Probably writing /patches/ to the LSB's would be more appealing. For example one could eliminate X from runlevel 2 and ignore the rest of the block. Best Ale --
