[Pkg-sysvinit-devel] Bug#542811: Bug#542811: Bug#542811: invoke-rc.d starts disabled

[Petter Reinholdtsen]

[Harald Dunkel]
> From init's point of view a service can be in one of 3 states in
> each runlevel: "enabled", "disabled" or "ignored". "insserv -r
> <service>" moves a service to the "ignored" state for all run
> levels. For a Linux-HA cluster I need this 3rd state.

Why do you need a 3rd state that is not enabled or disabled for the HA
cluster?

> The problem is that invoke-rc.d and init handle this 3rd state in a
> different way. This seems inconsistent to me.

I suspect it is because the third state is 'undefined', not
'ignored'. :)

> More important is the state of heartbeat on this host: It was in
> standby mode, i.e. the services provided by the cluster were active
> on another host. Maybe you can imagine that it can cause a lot of
> trouble if a postinst script calls invoke-rc.d during an upgrade,
> and an unwanted second instance of the service is started. It could
> corrupt a common database or filesystem, for example.

I have no problem understanding that this was unwanted. :)

I do on the other hand fail to understand why just disabling the
services in all runlevels and leaving their startup to the HA scripts
do not work.  Can you tell me more about this?

Happy hacking,
-- 
Petter Reinholdtsen