2012/2/27 Ante Karamatić <ante.karama...@canonical.com>:
> On 27.02.2012 12:27, Florian Haas wrote:
>
>> Alas, to the best of my knowledge the only way to change a specific
>> job's respawn policy is by modifying its job definition. Likewise,
>> that's the only way to enable or disable starting on system boot. So
>> there is a way to overrule the package maintainer's default -- hacking
>> the job definition.
>
> I've explained '(no)respawn' in the other mail. Manual starting/stopping
> is done by:
>
> echo 'manual' >> /etc/init/${service}.override
>
> That's all you need to forbid automatic starting or stopping the service.
>Not really appropriate for a cluster daemon to be doing though IMHO _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
