similar to: any plans to support pkgutil?

Hi everyone, I got a basic puppetmaster setup, which works well for Linux. I''ve setup a basic function: define remotefile($owner = root, $group = root, $mode, $source, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Hi all, I''m looking into a way to centrally manage installed packages on a fairly fine-grained level. We prefer not to blindly install every new update, but when a mechanism in which we can "approve" of a certain version or not. At first I was thinking about something external to puppet, but then I remembered that it''s possible in puppet to tell which version needs to

I thought I''d put this out there for anyone to save anyone who''s running 0.22.4 on AMD64 hosts a whole world of hurt. Basically, the libshadow-ruby1.8 package that Puppet (as of 0.22.4) relies on is broken for AMD64 in both Debian (Sarge+) and Ubuntu (all releases). The problem is basically just some non-portable code. I''ve reported the bug into Debian with a patch, so

Hi. I''d like to use exception handling in my custom facts. For example, in plain Ruby: begin buildno = '''' bcrelease = open("/etc/BCrelease") while (line = bcrelease.gets) line = line.chomp buildno = $1 if line =~ /^Build:\s+(\d+)/ end bcrelease.close print "#{buildno}\n" rescue print "No

I have written a custom package provider for the pkgutil utility on Solaris 10. Pkgutil replaces pkg-get which is not deprecated. All I did was modify the Blastwave provider to use pkgutil instead of pkg- get. I''ve tried two approaches to get the provider on to the client. First, I created a plugin. I created a module called package to contain the plugin. The only file in

Hi all, Today I came across something that I consider a bug. Would like to hear your opinions. Facts: - Using 0.22.1 from Debian Unstable on a Debian Testing machine - Recipes work on other machines The recipe in question is: # Keep home-dirs in sync file { "/home/tim": recurse => true, source =>

As everyone probably realizes, I''m getting swamped with incoming problems and tickets and I still need help triaging the tickets. James Turnbull has volunteered to help some, but I think we need more than one person. We''ve had a few people step in once or twice, but I''d like to be able to depend on Unreviewed tickets getting handled by someone else, rather

I''m trying to find email addresses of some of the speakers from Puppet Conf last week. They aren''t on the web site... maybe due to spamming concerns. Short of Googling, how can I get these? Also... are there slides available yet? What about video? Doug -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this

Can anyone point me to a procedure to install only the Puppet Agent on a Solaris 10 system for which I do not have root access? Everything I have found online involves using pkgadd and/or pkgutil, both of which require root privileges to run. --Ken -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and

> I''m on OSX, and I previously manually installed some test builds to help with > testing. Now when I go and install the official 0.26, the installer claims > that I have a newer version and refuse to install. Does anyone know how I can > fix that? This is a new "feature" in Mac OS 10.6. I am not even sure what it''s trying to accomplish but it gets upset

I need to do something like this node foo { $iface = pcn0 ... } # the template <%= network_<%= iface %> %>/<% netmask_<%= iface %> %> The idea being that a file would be built on the client holding the value of pcn0''s network/netmask Of course, I''m trying to avoid hard coding the interface name in order to keep my code portable. Thanks in advance

The original blastwave.rb would store "no pkg-get in /usr/sbin /usr/ bin" into @@pkgget if pkg-get is not found in the PATH. The patch below modifies blastwave.rb to store the first matching binary in the user''s PATH, or if not found, check the default location (puppetd''s PATH may not be sane) and if still not present and executable, correctly store as nil.

Hi all, I've got an ongoing battle with samba shipped with Sun Solaris 10 in it's current form (Samba version 3.0.28a) not wanting to talk to my OpenLDAP master correctly. Essentially, under certain conditions, this behaviour is observed, in the log.smbd: [2008/10/11 08:54:03, 1, pid=13610] libsmb/cliconnect.c:(1451) Error connecting to 192.168.117.150 (Connection refused)

Greetings, I have a solaris package stored on a puppet server. I''d like to be able to maintain the package on a client system without having to also keep a copy of the package file on the client system. (think lots and lots of packages) Checksums work okay for noticing changes on the fileserver, but it seems that I have to keep a local copy of the file as well. When I rev the package

I am using puppet 0.23.0-1 from Fedora Core 7 for a while and just realized that puppet use over 90% CPU every 30 minutes for about 10minutes. Anyone has the same issue? Barrow _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

Hi All I am trying to deploy the Solaris logadm pattern from http://projects.reductivelabs.com/projects/puppet/wiki/Logadm_Patterns. I dropped it in .../lib/puppet/type/logadm.rb However, I am getting an error message: err: Could not run Puppet configuration client: Munging failed for value "puppet" in class backup: Global resource access is deprecated And I have traced it back to

Dear OpenSSH friends : The Blastwave.org project is focused on providing quality open source software to Solaris and OpenSolaris users. Please know that your software is valued and one of the very first software packages to be offered by Blastwave well over 3 years ago. I have personally scraped together $100 for you but don't know where to put it yet. You have a PayPal link on your

I am trying to manage MySQL DB with puppet. So I create a class and would like to set the mysql SQL root password at the beginning. However, the "exec" will run before mysql-server has installed or started which make "exec" failed. how can I make sure the package has installed/run before "exec" task? class mysql-server { package { "mysql":

0.25.1 installed via gem on opensolaris 2009.06 I only see this error when my puppet master is set up to use mongrel root@puppet:~# puppetd --test info: Retrieving plugin err: /File[/var/puppet/lib]: Failed to generate additional resources using ''eval_generate'': No format match the given format name or mime- type (text/html) err: /File[/var/puppet/lib]: Failed to retrieve

On my Sun Enterprise 450, I installed ruby-1.8.4 from sunfreeware.com. That installed like a dream. I then downloaded rubygems-0.8.11. Untarred into /usr/local/src and tried to do a /usr/local/bin/ruby install.rb this is what followed and can someone help me figure out what to do? bash-3.00# /usr/local/bin/ruby setup.rb ---> bin <--- bin ---> lib ---> lib/rubygems <---