I've tracked down the issue. Under launchd in Mac OS X, processes are not allowed to daemonize, so we are starting god with the -D flag. The method that starts god in this case (run_in_front in lib/god/cli/ run.rb) doesn't check for the state of that option, and therefore syslog is started by default. I've put a patch up at http://github.com/ryanschwartz/god/commit/3366f0d753ecbf9d692537e5316e76bd99b21024 that takes care of this problem, as in the current state --no-syslog is only effective if god is being daemonized.
Thanks, Ryan On Dec 16, 11:47 am, Ryan Schwartz <[email protected]> wrote: > We're using god extensively in our production environment and I've > recently set up centralized syslog. The problem is that in testing > with our dev server, god is spewing around 2K entries per minute over > syslog, even with the --no-syslog option passed on the command line. > > I've looked at the code, and see that if the config option is set, > Logger.syslog get set to false, which should return immediately in the > load_syslog method. However, SOMETHING is still logging to syslog, and > furiously. > > Please to help, > > Thanks, > Ryan Schwartz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "god.rb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/god-rb?hl=en -~----------~----~----~----~------~----~------~--~---
