Re: How to disable services at startup... and keep them so.
On Wed, Dec 8, 2010 at 5:19 PM, Arthur Machlas <firstname.lastname@example.org> wrote:
> The move to insserv & lsb headers to deal with concurrent boot issues
> has thrown a bit of dust into the eyes of update-rc.d. I think if the
> user is working on a concurrent boot system, as squeeze is, they ought
> to consider handling scripts using insserv, /etc/insserv.conf and the
> lsb headers for each script in /etc/init.d (AFAIK insserv uses
> update-rc.d to ensure symlinks in various runlevels match lsb
> It will all be moot in a year or so anyway, once systemd gets tested
> out on Fedora. Probably not in time for wheezy, but perhaps wheezy+1.
Or upstart, which doesn't (yet?) have a mechanism to disable an init
script except editing the relevant "/etc/init/" conf file.
I'll be checking out systemd when Fedora adopts it (probably with F15)
but I find this fragmentation of init systems silly...