On 27.02.2012 11:37, Andrew Beekhof wrote: > I know, but whatever the admin specifies should over-rule the package > maintainer's defaults.
I agree and that's how upstart works. > From what you're saying, this is not possible with Upstart. Which is bad. I said it's an option, not that it's not possible :) /etc/init/ssh.conf defines ssh service/job. /etc/init/ssh.override is an override file that overrides everything from .conf. There is a catch, and that's that there's no 'norespawn' option. So, if a package maintainer defined 'respawn' in .conf, you can't really disable it without removing 'respawn' from job file. On the other hand, you can override default respawn behavior (ssh service): echo "respawn limit 1 1" >> /etc/init/ssh.override That would stop respawning if service fails more than once within the second. I'd say that non-existing 'norespawn' option is a bug. Best regards _______________________________________________ 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
