[06:03] <twb> I'm not sure if this is an ubuntu or an upstart question.
[06:03] <twb> I have a 12.04 chroot environment that I am installing packages into, as part of building a live image.  When I install a daemon package (e.g. cron), it tries to start itself by talking to upstart.  This fails (because it's chrooted).
[06:03] <twb> In sysvinit I would simply write a policy-rc.d that said "exit 101", which tells invoke-rc.d not to ever start such daemons.
[06:04] <twb> How can I get the same effect for upstartized daemons?
[06:07] <twb> In the past, it seems the least-worst approach was to diver initctl and put /bin/true in its place during the build.
[06:07] <twb> http://bugs.debian.org/571054
[06:10] <twb> OK, never mind.  I just tried writing a policy-rc.d and it seems that approach works now.  Yay!
[13:57] <tcr> Is seems like "start on" does not actually specify a prerequisite for a job to be started, but a pattern of events that if fullfilled will make the job be started automatically. Is that correct?
[17:30] <jodh> tcr: yes - see http://upstart.ubuntu.com/cookbook/#start-on and http://upstart.ubuntu.com/cookbook/#upstart-s-design-why-it-is-revolutionary
[19:26] <tcr> I have a job definition which contains "start on", "stop on" and a "pre-start script" - that's it. I'd have thought that creates a forever-running job, but it seems not to (status $job reports "Unknown job")
[19:27] <tcr> I want to create a job that perform some action, and if the action was successful, remains in the started state (so an attempt to start it again will be a NOP)
[19:37] <JanC> unknown job means exactly that: there is no job with that name
[19:37] <JanC> so either your job definition contains syntax errors, or you misspelled its name...
[20:25] <tcr> other jobs were started that depend on it. Is a .conf file checked for syntax errors before or while it is being processed?
[20:28] <xnox> tcr: .conf jobs are loaded when upstart starts and are not reloaded.
[20:29] <tcr> sorry how does that answer the question? :)
[20:29] <xnox> sorry, as far as I know syntax is checked on loading, but I'm not sure with respect to buggy shell snippets and what not
[23:00] <SpamapS> tcr: if you have Ubuntu 11.04 or later you can use init-checkconf /ec/init/foo.conf
[23:00] <SpamapS> xnox: upstart jobs are reloaded if they change, and the filesystem supports inotify
[23:02] <xnox> SpamapS: ok. I had wrong impression. still learning upstart.