[04:42] <Kamil_> can someone point me to some example upstart scripts? for example, something controlling apache or named would be interesting
[04:43] <ion> See /etc/init
[04:44] <Kamil_> is there a way i can see them without having to isntall the packages on my machine?
[04:45] <ion> Do you not have Upstart running on your system?
[04:45] <Kamil_> i have upstart on the system
[04:45] <Kamil_> i dont have anything controlling apache or bind
[04:45] <ion> There should be various jobs in /etc/init.
[04:47] <Kamil_> i created a script to execute a special build of named. it starts fine, but when i query its status, upstart doesnt seem to know about it
[04:48] <Kamil_> $ sudo start bind
[04:48] <Kamil_> bind start/running, process 2018
[04:48] <Kamil_> $ sudo status bind
[04:48] <Kamil_> bind stop/waiting
[04:48] <Kamil_> but it's definitely running
[04:49] <ion> It probably daemonizes. It’s easiest just to tell it not to daemonize. Upstart 0.6 has preliminary functionality for tracking forks, but it’s very easy to confuse that functionality. If you want to experiment with it, see the ‘expect’ stanza. Upstart 0.10 will handle that well.
[04:50] <Kamil_> thanks i will take a look at that
[04:51] <ion> That is, if you know exactly how the main process forks, feel free to use the expect stanza. If you’re uncertain, simply tell the daemon not to fork.
[04:52] <Kamil_> understood
[04:53] <Kamil_> another question, if there is a special stop command, is the correct place for that within a pre-stop script?
[04:53] <ion> Yes
[04:53] <Kamil_> thanks
[09:26] <Omahn> Is it possible to receive a log message from upstart of the exact command run from an 'exec' after all the variables have been populated?
[10:29] <Omahn> Will removing an upstart job from /etc/init automatically 'stop' the job (when removing a package) or should the package explicitly stop the job before removing the file?