Puppet users - Aug 2012 - How to handle ib_logfile size parameter in MySQL

I am trying to use puppet to create and manage mysql instances running 
under Ubuntu, probably using the puppetlabs-mysql module.

I am running into the issue that if you change the innodb_log_file_size 
parameter, mysql will complain and fail to start unless you delete the 
existing ib_logfiles before restarting mysql. 

I am mainly concerned about getting mysql running after an initial install. 
I don''t expect to change this paramater much, if at all, after that. 
However, since the debian package starts on install, it is already running 
before I can write the config file containing the innodb_log_file_size. 

I have only been able to think of inelegant and probably dangerous ways to 
deal with this. Has anyone come up with a solution for this? 


-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/qGikSlTIinQJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.