[09:52] can I tell upstart not to restart a job? [09:53] I have a job that already have a script that monitors it [09:53] dont put respawn in the job ? [09:56] steffen_b: checking my upstart script [09:57] steffen_b: respawn should be outside of script, pre-stop... right? [09:57] yep [09:57] so I'll comment it out. thanks [09:57] I feel a little guilty when using upstart because it is so much easier than init.d scripts [09:58] yes indeed [09:58] but general perception is [09:58] i dont know how this upstart works [09:58] that's why debian guys don't want it by default [09:59] at least this is what i get from our users (yavdr) [09:59] well , there is plenty of room for improvement in upstart (or the way ubuntu is using upstart) [10:00] what would you improve? [10:00] so from debian perspective i can understand it [10:00] check the shutdown handling [10:01] missing 'user' still compared to start-stop-daemon [10:01] missing states [10:02] if you get into the details , you get your hands dirty quickly [10:02] but i cant judge if its ubuntu or upstart [10:03] ok [10:03] * steffen_b is also just upstart user [10:03] in a ubuntu based linux distro [10:04] if my server start script run in the background, how do I use it with upstart? [10:05] I see the wiki but it mixes old and new releases [10:05] http://upstart.ubuntu.com/wiki/Stanzas [10:05] I guess I need to use daemon and than to tell it how to find the pid [10:05] i would say dont use a start script seperate from ubuntu job [10:05] argh [10:05] upstart job i mean [10:05] upstart [10:05] :D [10:06] one second [10:06] http://upstart.at/ [10:06] maybe I'll remove the part that run it in the background [10:06] http://upstart.ubuntu.com/cookbook/ [10:07] far better then the wiki [10:07] thanks [10:07] if the server you try to start has a mode to run in foreground [10:07] then use that in the job [10:08] if possible [10:08] easier to get it right then [10:09] having hard time with natty shutdown at the moment [10:09] ok [10:10] someone here who can provide me some helping hand to track it down ? [15:34] start myserver and stop myserver works [15:34] but when I'm trying "restart myserver" I'm getting stop/waiting after ~2 seconds [15:35] why is that? [17:26] bencc: are you sure stop & start both work correctly? (restart does exactly that, so there shouldn't be any difference) [17:46] good practice is to use ps -ef [17:47] and compare it to initctl list or status myserver [17:47] if pid is matching main process all is fine [17:47] if you use script section for the main process [17:48] make sure you use exec [17:48] so script and daemon get the same pid [19:53] JanC: they are working. not sure how I can check if they work correctly [19:59] just one example of what could go wrong: what if upstart thinks myserver is stopped while it's still shutting down so that when it's restarted too fast some resources that myserver needs are still in use? [20:00] checking logs might be useful [20:18] JanC: how can I check the logs? [20:18] myserver is supposed to halt until it really stops