doug.garst...@gmail.com (Douglas Garstang) writes: > 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.
See http://bugs.mysql.com/bug.php?id=27072 If you don't like this behaviour tell Sun. I use something like this, simplified (somewhat) which causes no problems. # Installation of MySQL server binaries class mysql::server { package { [ "MySQL-server-communitiy" ]: ensure => installed, notify => Exec[ "chkconfig_mysql" ] } # Configure the service. # - Do NOT ensure enabled as this is carried out by chkconfig_mysql. service { "mysql": hasrestart => true, hasstatus => true, require => Package["MySQL-server-community"], } exec { "chkconfig_mysql": path => [ "/sbin", "/bin" ], command => "chkconfig --levels 345 mysql on", unless => "chkconfig --list mysql | grep -q '3:$chkconfig_state.*4:$chkconfig_state.*5:on'", require => Package["MySQL-server-community"], } } Simon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---