Is there anything about the mongrel-service that would cause an application to behave differently? Besides the -B option to turn on debugging, are there any other tricks for me to get visibility to what is going on underneath the covers?
If I can't track down this issue, is there any to using mongrel_rails from a scheduler instead of the service?
Thanks!
--
-- Jay Turpin
"One test is worth a thousand expert opinions." - Bill Nye (The Science Guy)
_______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
