Todd, As of Yosemite, there is a new `launchctl blame` subcommand that you can use to identify why launchd chose to launch a particular service. In your case, the command would be:
$ launchctl blame system/homebrew.mxcl.httpd24 -damien On 26 May, 2015, at 19:53, Todd Wade <waveri...@gmail.com> wrote: > > Hello, > > I put http://paste.scsys.co.uk/483275 at > /Library/LaunchDaemons/homebrew.mxcl.httpd24.plist and it started apache, but > Server.app keeps logging 'com.apple.xpc.launchd[1] (homebrew.mxcl.httpd24): > Service only ran for 0 seconds. Pushing respawn out by 10 seconds.' > > Why is launchd trying to restart its target when it is already running? > > Thanks! > > _______________________________________________ > launchd-dev mailing list > launchd-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/launchd-dev _______________________________________________ launchd-dev mailing list launchd-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/launchd-dev
