search for: ehisey

I wanted to move a file from one directory to another because my co- worker didn''t like where it was being put by puppet. I went into puppet and changed the name parameter of the the file directive. I then created a new file directive to delete the old file, but I was wondering if there was a better way to do this. So, just to clarify, I went from: file {"myfile": name

Hello folks, I''m sitting here converting my static, simple classes/snmp.pp into a full module, and I''ve run into a bit of a brick wall. net-snmp is one of those wonderful programs that will only read two configuration files (it reads a few more, but only 2 are in /etc) - /etc/snmpd.conf and /etc/snmpd.local.conf. This means that my SNMP module is somehow going to have to

Does anyone have a technique for performing an exec the first time puppetd runs but then reverting to refreshonly => true state for subsequent runs? The basic idea is: file { "/etc/foo": notify => Exec["bar"] } exec { "bar": command => "Do stuff to /etc/foo", refreshonly => true } Should I use a fact that is unset based on a

As I sit here staring at my manifests (and pondering a module to control Glassfish), I''m pondering the best way to do a first-run of puppet to get the initial repositories and puppet configuration downloaded. My theory is that I''ll modify rc.local (or replace firstboot-tui, we don''t use it with automated builds) to run puppetd twice - once to request the certificate,

Hi. I wonder if it is possible to use more complex data structures in templates than simple variables and arrays? I have been trying nested arrays, as well as nested arrays and hashes, but nothing seems to work (more specifically, nested arrays seem to be flattened into a single array). Having only simple variables and arrays is a little limiting. Something like the Perl-based Template Toolkit

Alright, going ot ask this question in advance of doing bone headed tests. I have one application that does not understand the idea of /usr/local/ and insists on populating /usr. Of course it is closed source and commercial and it is the one they want to use. Below is the list of junk it shoves in /usr/share. Between the Type Reference guide and another email , I believe I can move this tree

On the Configuration refrence page the listen setting is descriped thusly: listen Whether puppetd should listen for connections. If this is true, then by default only the runner server is started, which allows remote authorized and authenticated nodes to connect and trigger puppetd runs. The question is when listen is set to true, does puppetd only listen for remote calls or will it listen for

Has anyone written a custom type to handle printers via lpadmin? Managing printers right is ithe single biggest PITA on my CentOS boxes since RH decide to remove the CLI interface. lpadmin works but usign that from exec seems like a waste. Making a type for it seems like it would be easy ( I say, while not knowing a thing about ruby). The main issue I am having is just setting up the darn things.

Is there a way to get the service type to only trigger if it is notified or is a file it is subscribed to changes? In a related issue what is the syntax for using notify across modules? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Can some point out what is wrong here? I get the follwing error with code structure in puppet. err: Could not create /root.ssh/id_dsa: You cannot specify more than one of content, source, target at /manifests/classes/set-root.pp # # set root files # class common-root { file { "/root/.ssh/id_dsa": mode => 600, owner

Can some one point out to me what I am missing? I suspect I have messed up the if/else some how. I am getting a '' Syntax error at ''{''; expected ''}'' at /srv/puppet/production/manifests/modules/apache/init.pp: 19''. According to the Language tutorial this should be correct. I am testing for an existence of a variable. If it exists chagne the

Andreas- On Thu, Apr 3, 2008 at 8:31 AM, Andreas Rogge <a.rogge@solvention.de> wrote: > Do you have SELinux enabled? When starting puppet from init.d with SELinux enabled it runs in xinitrc_t while it should (at least imo) run in unconfined_t. Running in xinitrc_t lead to *really* strange things. Everything way fixed once I deployed a policy that made puppetd run in unconfined_t. >