similar to: file serving question

Hi I am trying to push populate /home & subdirectories from the puppet server to all the Linux clients. I managed this with cfengine using rsync. But I am not sure how do I achieve this in puppet, do we have any inbuilt function for this. Also, is there a function for userdel like for useradd (user) groupadd(group). Any suggestion is appreciated. -- Deepak

Are exec resources triggered by notify events supposed to be run once for every event received or only run once per run irregardless of the number of resources that notified it? It seems to me that it gets run twice no matter how many resources triggered it. consider the following class: class dhcp { $prefix = "/usr/local/etc/dhcpd" $dhcpd_conf = "$prefix/dhcpd.conf"

Hi, I am running puppet-server 0.25.5 on CentOS 5.4. I defined a moudle in /etc/puppet/fileserver.conf as below: [files] path /tmp/puppet allow * I also defined a resource in /etc/puppet/manifests/site.pp: file { "/etc/passwd": owner => "root", group => "bin", mode => 644, } file { "/tmp/0909.txt": source =>

I''d like to extend my use of puppet to manage my desktop/notebook macs. As others have noted, the hostname of the mobile machines tends to change frequently, so basing the node name (in my site.pp) and the corresponding cert and private key names seems to be an issue. I seem to recall somewhat talking about this at Puppet Camp last week….. Generally my signing strategy is always to

hello again list!! I am attempting to work out how to serve files with puppet. Here is my fileserver.conf file # This file consists of arbitrarily named sections/modules # defining where files are served from and to whom # Define a section ''files'' # Adapt the allow/deny settings to your needs. Order # for allow/deny does not matter, allow always takes precedence # over

Is there any "correct" way to get puppetmasterd to not spam syslog with (mount[blah]) File source foo does not exist messages when using file source selection lists? I use them quite extensively, so it''s getting quite out of hand. The last resort will be to comment out the offending print statement! -- Russell A. Jackson <raj@csub.edu> Network Analyst California State

OS: FreeBSD 6.2-RELEASE Puppet: 0.22.4 OS: CentOS 5.0 Puppet: 0.23.2 Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, and when puppetd attempted to restart itself (using the init provider), it failed to start back up. Perhaps the init provider needs to close all file handles before executing the rc.d scripts? Additionally, I had puppetd update its

I am consistently getting the following error from puppetd when an exec resource is triggered by a refresh event: Apr 23 10:36:11 mailhub puppetd[37884]: Reopening log files Apr 23 10:36:11 mailhub puppetd[37884]: Starting Puppet client version 0.22.3 Apr 23 10:36:11 mailhub puppetd[37884]: Starting configuration run Apr 23 10:36:12 mailhub puppetd[37884]:

Folks, I have installed puppet my network and it works great .. I have configured it such a way that when I make changes in the server source fiels..it gets updated in teh puppet clients. As the document reads the puppet clients checks for any changes from the server every 30 mins. But is there is any opiton of changing this value to lesser time .. say 15 mins .. or is there opiton for the

Hi all, I’m exploring puppet for first time, trying to see if I can simplify my sysadmin tasks. So I decided to install it on FreeBSD 7 beta 3 and play with it, using another host as a server (Debian 4). As you can imagine I’m stuck. Here’s an excerpt of my super trivial manifest file: > node ''puppetclient.refactor.it'' { > package { > apache20: > ensure

After reading the rc.subr(8) man page and Newburns''s article on the rc.d subsystem[1], It''s clear that a rc.conf.d per service file structure is already natively supported on FreeBSD. I''ve verified this with my own testing: # echo puppetmasterd_enable=\"YES\" > /etc/rc.conf.d/puppetmasterd # /usr/local/etc/rc.d/puppetmasterd start Performing sanity check

hi everyone, i''m trying to roll out an .exe file for the puppet package provider "windows". my manifest looks like this: $package_source = "http://puppet.local.domain/base_check_mk/windows/check-mk-agent-1.2.3i1.exe" $package_name = "Check_MK Agent 1.2.3i1" package { "$package_name": ensure => installed, provider =>

Hi all, I''m running puppet agent as a onetime process. I would expect, if it can''t create the pid file, that it would exit non-zero. However, it seems to exit zero. Is there any way to change this? I''d like to know if it couldn''t run, and it seems that this is an error. [root@db1r1 ~]# puppet agent --onetime --detailed-exitcodes [root@db1r1 ~]# puppet

Hi All; I am using the PuppetDD 1.3 docs. I am attempting to run the following query: curl -H ''Accept: application/json'' -X GET http://localhost:8080/v2/resources--data-urlencode query@db_look Contents of db_look: ["=", "certname", "puppet-satellite"] However, I get no results with this... I also do not get an errors I do see this in the log

I have the following test case: file { sendmail-conf: path => "/etc/mail/${fqdn}.mc", owner => "root", group => "wheel", mode => 0644, links => follow, source => "puppet:///sendmail/${hostname}.mc" } $mail_dir = "/etc/mail" $cf_dir = "/usr/share/sendmail/cf/" exec { build-conf: command => "/usr/bin/m4

This is all ridiculously preliminary, but it''s late, I''m tired, and I think this kinda kicks ass. I''ve just committed what I think is the (finally!) conversion of file serving to REST from xmlrpc. I took the time to refactor how recursion works, and that probably has had a bigger effect on speed than the REST change, at least for larger directories and smaller

Hey, I''m exploring puppet-dashboard right now and I want to get the live aggregation running. But somehow I''m already failing at the puppet.conf entries ;) The Dashboard readme says: ### Live report aggregation To enable report aggregation in Puppet Dashboard, the file `lib/puppet/ puppet_dashboard.rb` must be available in Puppet''s lib path. The easiest way to do this

Hello, I have two Vmware images, with 256MB of RAM memory each one, running puppetmasterd for the server and puppetd for the client. It''s normal that my puppetmasterd and puppetd occupies almost 10% of RAM memory each one? They aren''t doing anything especial, just listening on the ports. Thanks.

I have a little issue with purging. I use: file { [''/etc/shorewall/puppet'',''/etc/shorewall/puppet/rules'']: ensure => directory, mode => 0700, recurse => true, purge => true, } but purging does not work, i can do a touch

Hello, I was wondering if there is a way to parse individual manifest files as part of a pre-commit hook in subversion. I am looking for something like puppetmasterd --parseonly, but that will work on individual files. This way I can reject a commit if it does not pass. Any ideas? TIA