search for: nagios_command

Hi folks, I noticed an interesting problem with the nagios_* providers especially in Debian. Besides writing to the wrong file (I fixed that issue) I''ve noticed there is a umask issue where the config files end up being owned by root with perms 0640. This causes nagios to spit milk out of its nose because it cannot read the configuration files. I came up with a kludgey solution to the

Puppet version: 0.22.4 facterversion => 1.3.7 rubyversion => 1.8.5 Given the following: file { yum_repo_d: path => "/etc/yum.repos.d", ensure => directory, recurse => true, purge => true } yumrepo { pkg_repo: descr => "Packages Repository", enabled => 1, baseurl => "http://Some/path/", gpgcheck => 0,

hi All, I''m a bit new to puppet. Is there a mailing list for puppet beginners?:) I have a service module called postfix, which defines file in a class: file { ''/etc/postfix/main.cf'': owner => "root", group => "root", mode => 644, content =>

...d using the content param are different) and people should wait until the REST support is here and then ideas like these will work? ;) Or are there any other ideas what could be wrong and how I could fix this issue? Ah and I use 0.24.4 on all clients, as well the master. The master has the latest nagios_commands improvements applied (for some other host) and the problemclient has the timeout patch applied. thanks a lot and greets pete. [1] http://github.com/duritong/puppet-djbdns/tree/master [2] http://reductivelabs.com/trac/puppet/ticket/1176 [3] http://reductivelabs.com/trac/puppet/wiki/UsingMongrelNg...