How can I make god LOUDER!

[Brad Gessler]

I've wired up God into a capistrano deployment script and I'm finding
it very frustrating how quiet god is. When I recycle my mongrels to
load the new app code, I run the following commands:

god -c latest_config_file_rev
god restart mongrels

If the config file is messed up god doesn't throw any error messages
at me. Here's the output from my cap script

--
* executing `god:config'
* executing "ls -xt /home/web_app/web/releases"
servers: ["web_apppreview.com"]
[web_apppreview.com:55555] executing command
command finished
* executing "sudo -p 'sudo password: ' god load /home/web_app/web/
releases/20081120213313/config/environments/staging/staging.god"
servers: ["web_apppreview.com"]
[web_apppreview.com:55555] executing command
** [out :: web_apppreview.com:55555] Sending 'load' command
** [out :: web_apppreview.com:55555]
** [out :: web_apppreview.com:55555]
** [out :: web_apppreview.com:55555] The following tasks were
affected:
** [out :: web_apppreview.com:55555] web_app-mongrel-staging-5000
** [out :: web_apppreview.com:55555] web_app-mongrel-staging-5001
** [out :: web_apppreview.com:55555] web_app-mongrel-staging-5002
command finished
--

All I know is that the "watches were affected", even if the new config
file is screwed up. When I watch the god log, I get to the bottom of
the errors:

--
I [2008-11-20 21:56:16] INFO: web_app-mongrel-staging-5001 restart:
mongrel_rails restart --chdir /home/web_app/web/releases/
20081120213313/config/environments/staging/../../../../../current --
pid /home/web_app/web/releases/20081120213313/config/environments/
staging/../../../../../current/tmp/pids/mongrel.5001.pid
W [2008-11-20 21:56:20] WARN: web_app-mongrel-staging-5001 restart
command exited with non-zero code = 1
--

Any ideas to make god louder? I scoured the docs and couldn't come up
with anything.

I also couldn't find anyway to have god log the individual mongrel
info into a single .log file; that would be great to keep tabs of!

[Cody Caughlan]

You can adjust the log-level via the

--log-level

switch

I prefer to use

--log-level info

level. YMMV

/Cody