[10:36] <o_cee> hello! trying to make an upstart script for spawn-fcgi, but ran into a problem.. how can I make sure the socket is chmodded 770, since I have to run the script from the upstart script without daemon mode?
[10:37] <o_cee> if I use daemon mode i can just stick it after it, but then upstart don't know about the status of the task..
[10:44] <o_cee> maybe easier to use port instead of socket
[10:59] <mbiebl> o_cee: why is the socked chmod 770 if you run the script in daemon mode?
[11:00] <mbiebl> Or do you chmod manually?
[11:00] <o_cee> mbiebl: problem is that the socket is 766 or something instead of 770
[11:00] <o_cee> yeah, don't know why spawn-fcgi does that, but i've solved it before by chmodding it afterwards
[11:00] <o_cee> but, seems port+addr instead of socket works fine, so i'll use that instad
[11:00] <mbiebl> o_cee: well, that you can do with a post-start script
[11:01] <o_cee> yeah, but the it wouldn't be all upstart, right?
[11:01] <o_cee> (never done any of these things before heh)
[11:03] <o_cee> ah post-start, yeah, but it seemed to get reset when spawn-fcgi is run? couldn't get it to stick.. either way, port mode works just as fine i think
[14:58] <voroskoi> hi
[23:20] <sadmac> ion_: ping