similar to: What's the canonical way to enforce permissions/ownership on a directory subtree?

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

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

hi, is there a way to specify that something is to be run only once, upon install of the package? i''m trying to automate the installation of some services and their requisite packages. some of them require setting up various things afterwards (user, passwords, etc). i know i could have it done via exec & onlyif. however there are obvious security issues with trusting the

Hi, I have a problem with running puppet with hiera based data. I am trying to cleanup user accounts on a range of servers (to have the same uid/gid). When I create existing account but with different uid/gid it doesn''t change files group ownership so I need to run a script which cleanups after cleanup ;-) I use the following code: --- :backends: - yaml :hierarchy: -

I have a module for windows nodes that is defined like: class ast_win { Class[''ast_win::env''] ~> Class[''ast_win::restart''] -> Class[''ast_win''] ast_win::env contains a bunch of scripts that modify the environment on the host machine. Mostly the PATH variable, but also other variables (e.g. http_proxy) that are required for

Puppet 3.3.1 // CentOS release 6.4 (Final) rpm -qa | grep puppet puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch puppetdb-1.3.0-1.el6.noarch puppet-server-3.1.1-1.el6.noarch puppetdb-terminus-1.3.0-1.el6.noarch Installed from yum packages: Running Transaction Installing : puppetdb-1.3.0-1.el6.noarch

so I have this sudo module that I''ve been working on: class auth::sudo { package { sudo: ensure => installed } file { sudo_config: name => "/tmp/sudoers", owner => "root", group => "root", mode => 0440, notify => Exec["sudoers-syntax"], source => [

I have a requirement to manage membership to groups in /etc/group. These members do not need to be virtual users. I don''t see a way to do this through virtual users @group. How are others doing this? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To

Puppeteers, I''ve seen things in the documentation to make me think this is possible but I''m not sure how to implement it. Here''s what I''d like to do: puppetd pulls down a config file, say httpd.conf BEFORE puppetd moves it to $path, I''d like to have it check it''s integrity with apachectl configtest IF configtest passes, then puppetd should

Hi all, I have an interesting one - Solaris uses a lot of commands to configure specific items. A simple example is coreadm. In this example: # coreadm -p "/var/core/core_%n_%f_%u_%g_%t_%p" will set the directory and filename to dump core files (with some expansion). The question is - how to get this to run only if the config has changed. I have come up with 2 options, neither of

Greetings, we are trying to setup puppetdb, nut our clients get the following error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: Failed to submit ''replace facts'' command for lxa7t.unix.lan to PuppetDB at puppetdb:8081: Connection refused - connect(2) Info: Retrieving

I''ve been using Puppet now for a month or so and I''ve come to a problem that may warrant an additional Puppet metaparameter. I''m advocating the addition of a metaparameter called "preaction" (or something like that), which will perform some arbitrary action before the resource is modified. There may be a way to do this within Puppet already (with some

Bryan -- I''m using the puppet augeas plugin at http://git.et.redhat.com/?p=ace.git;a=blob;f=modules/augeas/plugins/puppet/type/augeas.rb;h=2346c37d724d7607ed4e09b0413700bec2b7cbed;hb=HEAD I''m running into a behavior that I wouldn''t expect. I''d like to confirm an entry in sysctl.conf by changing the value if necessary or appending the key/value if it

PuppetDB is operating fine, but I can''t figure out how to disable it from listening globally on TCP 1099 or 58722 How do I disable them from listening globally without having to resort to iptables? $ lsof -i -n -P | grep java | grep LISTEN java 30115 puppetdb 22u IPv6 119118 0t0 TCP *:1099 (LISTEN) java 30115 puppetdb 23u IPv6 117236 0t0 TCP *:58772

HI, All our unix boxes under puppet are configured with the ''mailalias'' resource type as in : mailalias { "root": recipient => "linuxroot@fqdn", ensure => present } The majority of those boxes however don''t have /etc/aliases served out by puppet, rather, they simply have the installed default /etc/aliases locally.

Dear all, I''m trying to do this. Say for example, I want this link: "liblcgdm.so -> liblcgdm.so.1.8.0" to be present on the client only if "lcgdm- libs-1.8.0-1sec.sl5" is already listed. I already have this to create the link: file { ''liblcgdm.so'': ensure => symlink, name => ''/opt/lcg/lib/liblcgdm.so'',

Hi, I''ve got a ''define'' that I use to set kernel parameters in /etc/sysctl.conf using the augeas type. It works well, but I''d like to be able to add a comment line directly above my the parameter to explain what it does and why it''s been changed. We currently just add a comment in site.pp, but that''s not much use to local admins.

hello: i currently am using Puppet to run some commands in a sequence. there are two sequences of exec resources. we found that we cannot use require => Exec and it does not work at all as expected. here is some sample code. exec { "exec-AAA": command => "/bin/true", returns => 0, notify => Exec["exec-BBB"], } exec { "exec-BBB":

Dear all, I have this setup on Ubuntu 12.04 and using puppetmaster/puppet 2.7.14 and puppetdb/puppetdb-terminus 0.9.0 from puppetlabs. My puppetmaster also run puppetdb. I also use hiera in this setup. hadoop4 is puppetmaster and hadoop02 is puppet client. puppet node status hadoop4.west.net hadoop4.west.net Currently active Last catalog: 2012-06-05T23:23:33.159Z Last facts:

Hello, I have configured puppet and puppetdb (storeconfig) with postgresql and the service run and the collecting are good for example: I can make query with the next command and responds ok . [.........................] [root@master]# curl -X GET -H ''Accept: application/json'' http://127.0.0.1:8080/v2/facts --data-urlencode ''query=["=", "name",