| xnox | http://paste.ubuntu.com/1062218/ | 08:35 |
|---|---|---|
| xnox | can we please make upstart through warnings if start-stop-daemon is used in the upstart job | 08:46 |
| SpamapS | xnox: we recommend start-stop-daemon for switching users, so I don't think that would make much sense. ;) | 13:02 |
| xnox | SpamapS: yeah, especially in the ubuntu package, in the archive! | 13:02 |
| SpamapS | xnox: whats wrong with that job? | 13:02 |
| xnox | SpamapS: nothing wrong, it's just not upstartish | 13:03 |
| SpamapS | if you need to run pre-start's as root, you can't use setuid/setgid | 13:03 |
| SpamapS | you have to have something to switch user ids | 13:03 |
| SpamapS | I'm kind of surprised mongod doesn't have a --user argument tho | 13:04 |
| xnox | ok | 13:05 |
| SpamapS | xnox: http://upstart.ubuntu.com/cookbook/#changing-user | 13:06 |
| wavded | does upstart make sure a process is terminated? seems there are cases when it lingers around, wondering how to tune it | 18:19 |
| annath | Hey all, I have a wierd issue with a small service I've written using python. I'm using upstart to run it as a service. When the script runs as an upstart service, any calls to time functions (localtime, strftime, etc) come back in GMT. This doesn't happen if I just run the script on its own. Is there any way to fix this? I can't find anything on google relating to upstart and time. | 18:43 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!