[02:30] if I add my own upstart job, the command under "exec" will be run when the job starts; what does upstart do when the job is stopped? [02:31] PovAddict: kills the process that resulted from the exec [02:31] SIGTERM? [02:32] I believe so [02:33] can it be made to call a custom command on stop? [02:33] PovAddict: not sure if the current version can. You can make pre-stop do it, but I'm not sure if upstart will read it as a failure. [02:34] are there hooks to make 'status' give service-specific information? [02:34] not at present [02:35] to run a service as a different user do I just use 'su' in the exec, or is there specific support for that? [02:35] just use su [02:35] what about cwd? [02:36] I want to say there's a stanza for that.... [02:36] heh, undocumented-dont-rely-on-it stanza? [02:36] same as all of them [02:37] all of them? I'm sure you don't consider 'exec' undocumented and shouldn't be relied on! :) [02:37] PovAddict: chdir [02:37] I don't want to use things that may break later; I guess I'll just use a 'script' with cd and su [02:37] PovAddict: upstream's philosophy (and by upstream I mean Keybuk) is that until 1.0, anything is subject to change [02:38] really. AN-E-THING [02:38] * PovAddict >:o's at the lack of upstream config syntax highlighting in vim [02:39] why? 0.10 is going to have a different syntax anyway [02:39] heh [02:43] the current sysv scripts are set so it's killed on runlevels 0 1 6 and started on 2 3 4 5 [02:43] that's mapped to "stop on runlevel 0" etc, right? [02:43] stop on runlevel [016] [02:44] note I have a relatively old version, 0.3.9 :$ [02:45] that's what ships in ubuntu/fedora [02:45] yep [02:45] but since topic mentioned 0.5.1 *points* [02:45] and I have an old Ubuntu, I thought maybe newer Ubuntu versions had newer upstart [02:47] I don't think any distro is planning to ship a 0.5 at any point. everyone's skipping to 0.10 [02:54] docs mention /etc/init/jobs.d [02:55] /etc/init doesn't exist here, but I have stuff in /etc/event.d; should I put my job in there? [02:59] is the code in the script supposed to fork and return? initctl start mythingy seems to be blocked, as if it was waiting for the script to terminate [03:02] no forking [03:02] and /etc/init/jobs.d is the 0.5 location [03:02] I see [03:02] any idea why my 'start' blocked? [03:03] do you have a 'service' or 'respawn' stanza? [03:05] neither is mentioned in the documentation I'm reading :] so, no [03:05] * PovAddict goes to the wiki [03:08] http://upstart.ubuntu.com/wiki/Stanzas ok, so chdir *is* documented [03:08] sort of :) [03:08] adding 'service' worked \o/ thanks [03:09] i love the fact that it reloads config instantly using inotify