similar to: audit=>content

Hi, How should I handle the combinatorics when one config file must be built for a combination of possible classes? Take for example the amd automounter''s configuration file, which on Debian is found at /etc/am-utils/amd.conf. This is an INI style file which looks like: [fsname1] param1=foo param2=bar [fsname2] param1=baz param2=quag In my case I have one class of machines

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

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"

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

On Aug 27, 2006, at 9:55 AM, Thorsten Sandfuchs wrote: > hio, > me again :) > > In Debian, there is a mechanism to preseed debconf (configuration- > database for > the system) with decisions, before installing a package. Debconf > mussn''t ask > the user then. I wrote this pp for preseeding-support: [snip] Very cool. Seems like that''s something that

Assume the following question is in regards to Puppet 3.3.2. So my question is in relation to audit. file { ''/some/random/path/through/the/tree/to/a/file'': owner => ''luke'', group => ''rebelalliance'', mode => ''0444'', audit => all } And more specifically: will the named file be force-owned to luke with the

I''ve just tried this (we assume /opt/jetty-6.1.26 already exists): file { "/opt/jetty-6.1.26": owner => "jetty", group => "users", recurse => true, } ... but it''s taking an *age*. What''s the Right Way? Cheers, Robert. -- You received this message because you are subscribed to the Google Groups

Hello, I''ve created a little class which should unpack a 7z archive on Windows. The class has a parameter for passing in the archive version, so that I can trigger an update when a new version of the archive is available. A simplyfied version looks like this (requires 7z): class my_archive ($version = undef) { file { ''version'': path =>

Hi, I''m sorry if that''s a FAQ, I also know exported resources are a still experimental. So my problem might well be a design limitation of how exported resources are working. My issue: I''m trying to export a file resource that is created by an exec block. The file is exported fine and collected fine but it is always empty on the other host. The puppet snippet: class

Hi All.... I''ve got this configuration to manage bind, I want the exec to be run whenever anything under /var/named or the file /etc/named.conf gets updated.... file { "/etc/named.conf": owner => root, group => root, mode => 0644, require =>

Hello, I use some define in classes like class foo { define bar() {} } before in .22.4 i had require => Bar[''mybar''] on object and it worked. Now i have : err: Could not apply complete configuration: Could not retrieve dependency ''Shorewall-realize[shorewall.conf]'' at /etc/puppet/manifests/classes/shorewall.pp: for exemple. Do anyone knwo why it

Hi, I want to audit some files on content and planned to do this with puppet filebucket. Lets say for example that I have a list of audit_files as a parameter from puppet dashboard with a list of files to audit. Output from ENC for this particular parameter: audit_files: "[\"/etc/passwd\",\"/etc/resolv.conf\", \"/tmp/mawi\",

I''m trying to have a exec dependency on a service object that would keep it from being restarted if the exec fails. Unfortunately, the service gets refreshed regardless whenever the exec is run, failure or not. I''ve tried various combinations of subscribe/require/notify, but can''t find an elegant way to not restart the service when the dependency fails. I must be

Hi, i wanted to know how you handle case when classes or define need to communicate between them. For exemple i got an ftpd define and a apachevhost define. Both need to know the path where the vhost is set and this path is defined by the ftpuser home''s directory. How can i ask information from other define or other classes ? we allready seen that tag are not reliable as they

Was file bucketing changed as part of this release or is this a bug? When I look in my bucket folder I see: drwxr-xr-x 2 puppet puppet 4096 Mar 17 00:04 5222e054e7bc6248f2e9b9146f75aff5 drwxr-xr-x 2 puppet puppet 4096 Mar 17 00:04 3255ad7efedebfd3eccbba74845002a1 drwxr-xr-x 2 puppet puppet 4096 Mar 17 00:04 f8569b1c57819072c37b36bd3814e328 drwxr-xr-x 2 puppet puppet 4096 Mar

In my puppet client I have puppet.conf defined puppet server as mypuppet server = mypuppet.example.net Not sure why the puppet client puppet-test is still sending these noises to the syslog Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 daemon.error] Could not find server : getaddrinfo: node name or service name not known Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911

Hi all, I''m having a stupid moment getting a remote file bucket working. My client only file buckets locally, not remotely. I have this site.pp: ********* filebucket { "main": server => "puppet" } File { backup => "main" } node ''default'' { include test } ********* and this test module: ********* class test { file {

notice: /subject.sol1.net/virtual_mail_server/File[/etc/postfix]/checksum: checksum changed ''{time}Thu Jan 25 16:31:08 EST 2007'' to ''{time}Thu Jan 25 16:36:39 EST 2007'' I know there''s something weird in the directory modification detection that causes the next run after things actually change to suffer from this problem, but I''m getting it

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

I''m using the SimpleText recipe and Augeas plugin to modify files in place. I''d like to notify the appropriate File resource that a modification is about to take place so puppet can backup the file. Maybe this is already possible but I haven''t found any examples or documentation on how to accomplish this. I think a natural way to do this would be to use the subscribe