=== jY- is now known as jY [15:32] hi, I'm searching (fruitlessly) in the docs for some info about any provision upstart makes for restarting processes without sending them a TERM and then booting them again, many bits of software (I'm talking Unicorn and Resque) here can be gracefully restarted using signals… [15:44] codebeaker: "man 5 init" has lots of information on what I think you're asking for. [15:44] ah, cool - thanks [15:44] codebeaker: if you're referring to maybe sending SIGHUP to a process, "man initctl" and search for SIGHUP. [15:45] thanks, it's not solely about SIGHUP, example "Resque" (background workers for web apps) expects USR1 for graceful restarts [15:45] but thank you in advance for the guidance [15:46] np. in init(5), also see the section on "kill signal". [15:46] * codebeaker offers a bow [15:46] cheers [15:46] any time [16:11] codebeaker: the codebook also has lots of good info [16:12] thanks JanC [16:12] teh cookbook I mean ;) [16:12] http://upstart.ubuntu.com/cookbook/ [16:24] cookbook > wiki [16:25] I hadn't realized the wiki was so badly outdated until I happened to click the wiki homepage [16:38] also, I recognized there's no obvious stanza for running a job as a specific user, is it the script author's responsibility to `su` and run? (Writing a wrapper for Unicorn, which is a forking server supporting specifying which user to run as, but opens it's log files as root before forking, and that's making a problem) [16:44] yes. we're planning to add setuid and setgid stanzas as the code is already in upstart for user jobs. [16:45] sounds like Unicorn needs to be fixed. [17:00] ok, jhunt yeah, looks like, after the first request it hits (failed, or otherwise) then it sets the log permissions correctly, (and owner) [17:00] but it's kinda lame [17:02] thanks again jhunt - I really appreciate your time [17:10] jhunt: maybe its time we took the wiki down, or at least added a massive disclaimer that its there for posterity only?