[00:46] dcorbin_work: thats because those are *events* not states.. so you have to emit getUpdatesComplete *and* runlevel [00:47] dcorbin_work: if you want to check state, use pre-start... [00:48] dcorbin_work: [ "`runlevel`" = "N 3" ] || stop [00:51] wereHamster: yes start/stop , or the 'start on/stop on' clauses are the only things that will change a job from its default goal of stop to start. [08:29] SpamapS: does it mean I can edit the .conf file and upstart will start or stop it? Or do I have to explcitly tell upstart that I want the state changed? [08:29] wereHamster: if you edit the conf file, and then an event you listed in the start on or stop on is emitted, then the job will be started [08:30] wereHamster: the file changing wouldn't cause a start or stop on its own.. because upstart is event based, not state/dependency based [08:32] bummer :( [08:38] wereHamster: why bummer? [08:38] the behavior is well defined. [08:39] fairly easy to automate things when you can reliably predict the behavior. [08:41] wereHamster: good luck.. heading to bed [09:58] does upstart not source /etc/profile.d/*? [11:06] wereHamster: of course not, why would it do that? [11:08] because that's where I set $PATH, so it's avaiable to all users and scripts in the system [11:08] wereHamster: /etc/profile & ~/.profile are only to be read by a login shell... [11:44] wereHamster: maybe you can use the 'env' & 'export' stanzas to get the result you want? [11:47] yep, that's what I'm doing [11:47] but it's kindof duplication if I have to put the same path into two separate files [11:47] that's my only concern [11:47] you can maybe source it from the same file? [11:48] true. Or use exec bash --login -c .. in the upstart file [11:48] why do you need a special path BTW? [12:01] I guess you could also set & export $PATH in an initramfs (if you use one)? [12:48] because I'm installing software which is not in ubuntu, and am installing it into /opt [13:43] well, you can always use the complete path when referencing a binary [17:46] If I make a change to /etc/init/mysql.conf, will it get overwritten if I upgrade the mysql package? [17:47] got my answer