similar to: Run command when file changes

There was a discussion a while ago about adding inheritance to definitions. There is a need for a way to specialize parameters while allowing passing other options. This comes up with remotefile where it would be nice to have a default server location but not specify all the parameters (and their defaults) in the definition. Was there a change to the syntax? Is there a way to accomplish this?

What is the right way to write definition so that defaults can be overriden? $puppetdir = "puppet://$server/files" define remotefile($source, $owner = "root", $group = "root", $mode = 0644, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

I am trying to write a definition that downloads and extracts a tar file if the destination directory does not exist. The tar file won''t change and does not need to be download and extracted if it changes. The definition I am using now is: define remote_tar($source, $directory) { remotefile { "/tmp/$name.tgz": source => $source, } exec {

Hi, I had a working puppet setup using version 0.22 until the ruby security patch bit me. I tried upgrading server and clients to 0.24.1 however my old manifests don''t seem to work anymore. When I run puppetd on the client I see lots of messages like: err: //Node[waterbuck]/yumupdater/Remotefile[/etc/cron.hourly/yumupdater]/File[/etc/cron.hourly/yumupdater]/ensure: change from absent

I''ve been seeing this for a long time now... Got a class like: <snip> class iptables { package { iptables: ensure => latest } service { iptables: enable => true, ensure => running } remotefile { "/etc/sysconfig/iptables": mode => 400, source

Hello List, We are using puppet to manage a growing number of Debian Etch based servers (currently 70). Since upgrading to 0.22.4 we encountered a problem when services do not restarted on puppets request. For example the Nagios remote plugin executor daemon (nrpe). It''s running daemonized and its confiugration is located in /etc/nagios/nrpe.cfg. This file is managed through puppet

Hello. I''m a long time cfengine user, some might say sufferer, and I have finally managed to get around to experimenting with Puppet. So far I''m very impressed. I am trying to get puppet to configure the openntpd config file, from an ERB template, based on the node definition in the site config. What I''m trying to understand is why when I define a variable in a child

"Service and class definitions are scoped just as variable assignments are." But what about types? Here''s an example: class solserver inherits server { remotefile { "/etc/shadow": mode => 400, group => staff, source => "solall/etc/shadow.server" } Is it possible to just override the "/etc/shadow" definition for

Hi, I just upgraded to puppet 0.20.0 today after a short time playing with 0.19.3. The docs say to use the uppercase form for types but that seems to break for me. When I updated the remotefile function to use the new way, the puppet clients complain about objects not being found. For example: ----- OLD WAY (works, just with deprecations) ----- define remotefile (...) { file { $name :

Hi, is there a way to make sure a file is installed only if a certain package is installed on the client? e.g. I want to distribute the client key for NX via puppet. However I only want to install these files if package ''freenx'' is installed on the client. I tried adding ''require => package["freenx"]'' but then puppetd complains it

Hi, I''m exploring Puppet and have hit a rather weird problem. The puppetmaster server is running CentOS4, fully updated, with puppet installed from the dlutter RPM repo, version 0.20.0-1.el4. I tried adding the remotefile function definition from http://reductivelabs.com/projects/puppet/documentation/installation.html in /etc/puppet/manifests/utils/remotefile.pp but when I start

I am having SSL difficulties setting up a new puppet client: Client: fedora (rawhide) using 0.23.2 Server: centos 4.4 using 0.22.3 After initiating contact with puppetd --test --server=puppet.myclient.com, I see the CSR on the server. After signing it, and running puppet again, I get the signed certificate, but also see: err: Could not retrieve configuration: Certificates were not trusted:

I tried using $name in this manner: remotefile { "/etc/auto_direct.local": mode => 644, source => "solall/$name" } (The remotefile function is handy, BTW) When I use $name here, instead of specifying the actual path to the file (solall/etc/auto_direct.local), puppetd ends up making /etc/auto_direct.local an empty directory. Shouldn''t $name

Hello The following chunk is within a class definition. ${name} is being exchanged with an empty string: remotefile { "/${server_xml}": owner => tomcat, group => tomcat, mode => 600, source => "${ftoe_src_prefix_dev}${name}.jvm1" } However in the following chunk, lower down in the same class definition, ${name} is being exchanged

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''

Howdy, Found out about this project while looking for via ONLamp''s FreeBSD build system article. After finding cfengine a tad arcane, this project seems like a good fit for my setup. I''m still at the tinkering phase, but I envision this thing bootstrapping and maintaining several FreeBSD installs which have different CPU''s and packages. The Good News:

Has the component/type defaults syntax changed for 0.22.x? I have a component: <snip> define remotefile($owner=root, $group=root, $mode, $source, $backup=false, $recurse=false, $groupname="default") { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Hi, I''m trying to use several sources to pick from in a remotefile statement: remotefile { "/etc/sudoers": mode => 0440, source => [ "config/apps/sudo/sudoers.${host}", "config/apps/sudo/sudoers" ], sourceselect => first } But it doesn''t seem to work. I get an error like this: "File source

It seems to me that when you setup an environement for a cron it just recreate the crontab at each run even if the cron has not changed. Seems it does not recognize actual environement settings. I put 2 environement and i got: info: Writing cron tab for aqadmin /linux/cron=puppetdcron/environment: environment changed '''' to

I''ve been using puppet for a while but I just recently decided to start using it to manage crontabs. It works great but puppet is reporting (and being very noisy about it) every time it does a run even when there is nothing in the actual crontab to change. I think this is happening because I''m setting defaults for the Cron type, which I should be able to do. Right? eg: Cron {