On 11/21/2011 01:19 PM, Mo Morsi wrote:
there will still be some sql that gets logged when
conductor/dbomatic
initially comes up, regarding querying the db for activerecord model
information. Unfotunately nothing we can do about that bu this removes
the regularily repeating sql log statements
---
src/dbomatic/dbomatic | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/dbomatic/dbomatic b/src/dbomatic/dbomatic
index 2b6aed7..24e7e30 100755
--- a/src/dbomatic/dbomatic
+++ b/src/dbomatic/dbomatic
@@ -234,6 +234,7 @@ def refresh_instances
# before forking, and then have each child re-establish their own connection.
# We also have to have the parent re-establish the connection so that
# "collect_accounts" works properly
+ ActiveRecord::Base.logger = nil
ActiveRecord::Base.remove_connection
accounts.each do |account|
pid = Process.fork
Ack. Looks harmless enough. I wasn't able to verify
because dbomatic
seems to be broken. But that's unrelated to this patch:
#
2011-11-30 12:16:41 INFO DBOmatic starting up
#
2011-11-30 12:16:57 ERROR
/usr/lib/ruby/gems/1.8/gems/activesupport-3.0.10/lib/active_support/dependencies.rb:
#
304:in `depend_on': No such file to load -- lib/aeolus/event
#