similar to: file_splice Hack

Hey all, I finally found some time to update the munin module and here it is. please configure your munin-nodes directory in: munin/manifests/init.pp prior to using this module. you also need ''file_splice'' a.k.a. the bracketeditor. see here: http://mail.madstop.com/pipermail/puppet-users/2007-June/003466.html and a slightly changed version of ''remotefile''.

Hello all. Probably this question has already been posed in the context of another software, but I am unable to find it. I would like to implement a module which should manage munin-clients as well as the munin-server. Here is what I am thinking about implementing: - There are two classes: munin::client and munin::server - munin::clients'' configuration will be managed automatically.

I have copied the simple text snippets into a pp file and set a host to attempt to add lines, but regardless if the line is there or not, it still adds it... what am I doing wrong? in definitions/linetests.pp: define append_if_no_such_line($file, $line) { exec { "echo ''$line'' >> ''$file''": unless => "grep -qe

Hi, I wanted to set the project property of a Solaris user after realizing the user. Have already created the project by adding a line to /etc/ project. The user is created in virtual::user class wich is inherited by the target class to be able to add the project property. The project of the user xxxx gets not set properly and remains default when I use the project property ! Had to fall back

I''m not sure if this has been posted previously, but I couldn''t find any information on it. I added a cron job via the cron type and it installed properly. Next, I removed the cron type from the manifest. The result was that, while the entry was no longer in the yaml file, the cron entry was not removed! Is this a bug, or the way that it is supposed to function? Thank you,

Hi .*, with the first puppet run on a freshly installed system all custom types and providers a synced. As you can see from the output for some reason puppet tries to load the providers before the types and therefore the custom provider loads throw an error. It looks like the load happens alphabetically ordered, such that providers are loaded before the types... Anyway the puppet run afterwards

what is the best way to handle package conflicts between classes? for example, below, i have the following two classes defined and both include a "package { "perl-LDAP" }", so when used separately they work as expected but when i need to assign both classes to a node i get a conflict. error: "Duplicate definition: Package[perl-LDAP] is already defined" thanks

Hi all, I am new to puppet and also newcomer in this group. I heart good things about puppet and I decided to give it a try 2 weeks now. After reading various documentation, I began using the complete configuration collection of puppet modules (thanks to David). But I have a problem with the munin module. It works fine, except that it seems to not export virtual ressources. Let me give more detail

I have a situation where I''d like to perform some actions when a node is removed from a class. I have a few (homegrown) services that install ssh keys in authorized_keys and it''s possible that a node may have the service enabled and disabled during it''s lifetime. When disabled I''d like to clean up the ssh keys for security reasons. This brings up the broader

Hi, I have this resource definition: ssh_authorized_key { "nagios@login2": key => [REDACTED] user => "nagios", type => "ssh-dss", require => Service[''nis''], } This nagios user comes from NIS, yp.conf and nsswitch.conf are handled by puppet and configured before the key. I still get an "User does not

This was a fun one to track down... I was trying to use the append_if_no_such_line script from the wiki and it was working fine EXCEPT when I threw a notify at it. The notify appears to completely ignore both unless and onlyif within the exec for some reason. If I put the same test in the actual command line, it works fine. Example: unless => "/bin/grep -Fqe ''$line''

We need to manage /etc/passwd where there would be one line at the very end of the file to restrict access to all users not explictly allowed: +::::::/sbin/nologin If using delete_lines and append_if_no_such_lines (similar to this one at http://www.debian-administration.org/articles/528) to manage access control, each time a few new users got appended to /etc/passwd file, the above line would be