Ticket #363 (closed task: worksforme)
OS-X: how does one use launchd to start a buildbot?
| Reported by: | warner | Owned by: | warner |
|---|---|---|---|
| Priority: | major | Milestone: | undecided |
| Version: | 0.7.9 | Keywords: | |
| Cc: | regener |
Description
'regener' recently changed the UsingLaunchd page with the following comment:
- Just simplifying a bit. You don't need to kick the twisted process off, once set up, you can just specify buildbot directly.
I'm not sure this is true.. I was under the impression whatever launchd runs needs to *not* daemonize. Otherwise launchd thinks that the process-for-which-it-is-responsible has exited, and ought to be restarted.
Rather than put a discussion in the UsingLaunchd wiki page itself, I figured we could use a ticket for the conversation.
regener: with the change to 'buildbot start' that you describe, do you see evidence in the Console.app logs that launchd is continually restarting the process?
cheers,
-Brian
Change History
Note: See
TracTickets for help on using
tickets.
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
Console.app has no recent mentions of launchd or buildbot and it's been running for a week or two, so as far as I can tell, it is not restarting. Also that sort of activity would show up in the buildbot waterfall, correct? It would look like the server was restarting all the time.
So far as I can tell, it is stable and working and when the machine restarts my buildbot slave and master on that machine start right back up...