[00:45] sbuild does not.. something w/ the aufs I think [02:54] So - I'm trying to issue a 'killall' command to clean stuff up before a job is started. But if a matching process isn't killed, I guess killall returns a failed exit code (?) because then the job "fails to start" [02:55] What are you killing in pre-start? [02:55] ion - killing old instances [02:56] This process sometimes doesn't clean up after itself [02:56] And it creates child processes [02:56] Shouldn’t that kluge be placed in post-stop? [02:56] It also binds to a port, so if any of the worker processes still exist on the next attempt at restarting it, you get an address in use error [02:56] I plan on putting it in both places [02:56] Or perhaps pre-stop. [02:57] Why not pre-start? [02:57] Isn’t that redundant? [02:57] Well, if I had to choose, pre-start would be the best place in that case [02:57] Because I don't care about the workers except when I'm trying to start a new process [02:57] So cleaning up after is much less important than preparing at the beginning [02:58] When Upstart thinks a job is in the stopped state (which is a prerequisite for starting something), it *should* be. [02:58] It’s very nasty to leave processes just laying around even though the job claims to be stopped and then try to clean them up just before starting it again. [02:58] Then why not just do it on both ends? [06:26] to get a script working, do i just copy my conf file into /etc/init? and then just do 'start script'? [14:45] is it intentional that daemons started with upstart (ubuntu 10.x) don't inherit limits from /etc/security/limits.conf ? [14:56] so if i create an upstart conf, shouldn't i be able todo 'start myscript' immediately? [14:57] codebeaker: upstart doesn't use pam currently. [14:58] ok, so it's planned/unplanned/etc - but the limits stanza is just as sane (once you know about it) [14:58] frewsxcv: yes, assuming the script has valid syntax - try running "init-checkconf file.conf" [14:58] I've inherited a somewhat badly written upstart script via a ppa package, and was surprised that the software basically doesn't work out of the ppa, didn't know that there was a limits option [15:00] l [15:01] jhunt: i don't have that command [15:02] assuming the file is in /etc/init/, run "initctl log-priority debug && touch /etc/init/myfile.conf". Then, tail you system log and look for the name of your .conf file. [15:02] Upstart will have logged if it has read it or if it is syntactically incorrect. [15:03] frewsxcv: alternatively, do this: http://upstart.ubuntu.com/cookbook/#older-versions-of-upstart [15:03] frewsxcv: (just to check the code blocks) [15:06] thanks jhunt [15:06] frewsxcv: np.