+1 On Thu, Dec 17, 2009 at 3:01 PM, Jesse Wolfe <[email protected]> wrote: > As suggested in the ticket, set :reconnect to true. Our in-house Rails > experts suggest that this is unlikely to cause any problems. > The setting is silently ignored before Rails 2.3 > > Signed-off-by: Jesse Wolfe <[email protected]> > --- > lib/puppet/rails.rb | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/lib/puppet/rails.rb b/lib/puppet/rails.rb > index 98d8297..98c0e3d 100644 > --- a/lib/puppet/rails.rb > +++ b/lib/puppet/rails.rb > @@ -54,6 +54,7 @@ module Puppet::Rails > args[:username] = Puppet[:dbuser] unless Puppet[:dbuser].empty? > args[:password] = Puppet[:dbpassword] unless > Puppet[:dbpassword].empty? > args[:database] = Puppet[:dbname] > + args[:reconnect]= true > > socket = Puppet[:dbsocket] > args[:socket] = socket unless socket.empty? > -- > 1.6.5 > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Developers" 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/puppet-dev?hl=en. > > >
-- ----------------------------------------------------------- The power of accurate observation is commonly called cynicism by those who have not got it. ~George Bernard Shaw ------------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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/puppet-dev?hl=en.
