similar to: subscribe exec to a dir fails

Hi all, One of the major new features in the upcoming release is that Puppet now uses a graph library internally to handle resource relationships. The big benefit to all of you is that you can use this library to turn these graphs into images. The trick, right now, is adding --graph when you run puppetd. This creates .dot files, which can then be interpreted by the

Hi, For the past week, I have been trying to figure out the best way to do package management with Puppet on an Ubuntu system. I have studied many solutons I found on the web, but none of them seem to do exactly what I want. Among other things, I have tried everything that is discussed here: http://groups.google.com/group/puppet-users/browse_thread/thread/af7349171a5821a4/db96b809c97f6006 but

What with the impending release and a now fixed bug nagging me, I''m testing puppet [2556] from subversion. There have been changes in packages, I used to have Package { provider => "aptitude", } in my default.pp, but that doesn''t work anymore, and changing package to type or removing the declaration doesn''t help. How do package providers work now?

Hi all, I need to write an aptitude provider for Debian. How should it differ from apt? Can I just s/apt/aptitude/g, or do I need to do something else? Any other weird behaviours I should look for or whatever? I''ll make it a subclass of apt (and since Deb seems to specify aptitude as the default now, maybe apt should subclass aptitude), so any dpkg answerfile work should work on

Hi all, I''m attempting to use the puppetlabs-firewall module. In testing, rules are enabled in a random order, so it seems necessary to utilize puppet stages to guarantee proper ordering. I created a module to organize my firewalling. It consists of localfw::pre to open the INPUT chain for established and related connections, localfw::default for most normal rules, and localfw::post to

So here is my manifest: class aguu { exec { "update": command => "apt-get update", path => "/usr/bin/" } exec { "upgrade": command => "apt-get upgrade -y", path => "/usr/bin/" } } It it supposed to run apt-get update + upgrade

Guys Compliments of the festive season to everyone. Ive looked at mcollective plugins from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki And I tried / installed some of them. What im looking for is a method or really a mcollective plugin to ''aptitude safe-upgrade'' on my test VMs. Would anyone have a solution or method on how I can go about this. The only

Using ```puppetlabs/apt``` in a puppet provisioner for vagrant. the module is installed in puppet/modules and I''m getting a strange Dependency cycle error. the code in the manifest file: # Run apt-get update when anything beneath /etc/apt/ changes #taken from https://blog.kumina.nl/2010/11/puppet-tipstricks-running-apt-get-update-only-when-needed/ exec { "apt-get

Hi, I''ve inherited a puppet setup for automating php installation and extension management. We''re on Debian and we''ve encountered a strange issue that I''ve traced down back to puppet I think. I''ve stripped back the configuration and made the problem reproducible, logs and config pasted below. 1. php5-common, php5-memcache, and php5-mysql are all

I am trying to use puppetlabs apache module on CentOS to install mod php package. class {''apache::mod::php'': } It returns error "Error: Could not find dependency Package[httpd] for A2mod[php5]". I am using Puppet 3.1 version. Do I need to call class{''apache'': } explicitly to get mod-php install working? If I try that as follows then it

Hello, I am examining whether puppet meets our needs. I can''t find the answer to two questions I am looking to answer, hopefully someone can help. 1. Can puppet be used to manage different classes of the same computers, e.g. do something on the apache test farm, if it works then do it on the apache live farm; and is this done cleanly? 2. How are package updates (e.g. yum update/yum

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I''m trying to figure out why exec{} which subscribes to a file, doesn''t get triggered when the file is touched by puppet. I''ve got the following: exec { "/usr/sbin/postmap /etc/postfix/checks/access": refreshonly => true, subscribe => File["/etc/postfix/checks/access"];

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 folks, My site uses puppetmaster 3.2.3 together with Debian wheezy, but I want a few packages from wheezy-backports, like iceweasel and libreoffice. The former I''ve installed as follows: package { "iceweasel": ensure => ''22.0-1~bpo70+1'', provider => ''apt'', install_options

Hi again, From examples I have gleaned the following snippet for manifests/site.pp Package { provider => $operatingsystem ? { FreeBSD => freebsd, #FreeBSD => ports, debian => aptitude, redhat => up2date }} Are there providers documented somewhere? I''m not sure where to look, and I haven''t come across it in my

Anyone care to share how they handle yum updates? We have a script that runs yum update nightly and then emails us the results when there are packages to be updated. Ideally I''d like a way to keep a class in site.pp that can be uncommented to run yum update -y after the update list is reviewed by a human. Tim

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

I just upgraded to .22.3 from .22.1 and now i got several error messages. I havent found why i got them. Nothing has changed but still there is error and i cannot correct them: err: Package[lsb-release](provider=aptitude): Could not find latest version i run debug: debug: package provider aptitude: Executing ''/usr/bin/dpkg-query -W --showformat ${Status} ${Package} ${Version}\n

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

Hello Im just been working with puppet, the first usecase i have is to set up a system to create users and then push ssh keys on this machines in the create users .ssh files. I just started with puppet so i am a bit cluesless, Can someone push me in the right direction? Im having a centos enviorment. -- You received this message because you are subscribed to the Google Groups "Puppet