I've got a mostly working puppet manifest for mysql, except for one problem.
I'm using the RPM from the MySQL web site, and the packagers of this RPM in their infinite wisdom decided that the mysql service should be automatically started when the RPM was installed. This confuses puppet. The RPM is installed, and the service is started in quick succession. When puppet runs a 'service check mysql', since mysql hasn't fully completed it's startup yet, the service script returns that MySQL isn't running, and puppet goes ahead and starts a second copy. Any ideas of how to get around this? Doug --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
