----- Original Message -----
> From: "Andreas Ntaflos" <d...@pseudoterminal.org>
> To: "The Pacemaker cluster resource manager" <pacemaker@oss.clusterlabs.org>
> Sent: Wednesday, February 29, 2012 1:38:08 PM
> Subject: Re: [Pacemaker] Upstart resources
>
> On 27/02/12 13:09, Ante Karamatić wrote:
> > 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.
>
> Does this work in Ubuntu 10.04? As far as I remember the discussion
> on
> this problem in Launchpad, the consensus was something like "too late
> for Lucid".
From what I read (upstart.ubuntu.com/cookbook) when I needed to disable Upstart
jobs in 10.04:
With version 0.6.7 - rename job config to not end with ".conf" or comment
"start on" line with #
^^^ this is a little misleading since 10.04 (Lucid) has v0.6.5-8 but the above
seems to work fine
The ".override" file option described above is listed as available since v1.3
(this option seems much clearer/cleaner/obvious). Version 1.3 isn't released in
Ubuntu until 11.10 (Oneiric) according to packages.ubuntu.com
Unless I'm missing something...
Jake
_______________________________________________
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
