similar to: Solaris ingores server variable

Seems that blastwave is all about pkgutil now. Are there any plans to support this? Best, Adam --~--~---------~--~----~------------~-------~--~----~ 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 unsubscribe from this group, send email to

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

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

I am having SSL difficulties setting up a new puppet client: Client: fedora (rawhide) using 0.23.2 Server: centos 4.4 using 0.22.3 After initiating contact with puppetd --test --server=puppet.myclient.com, I see the CSR on the server. After signing it, and running puppet again, I get the signed certificate, but also see: err: Could not retrieve configuration: Certificates were not trusted:

What is the right way to write definition so that defaults can be overriden? $puppetdir = "puppet://$server/files" define remotefile($source, $owner = "root", $group = "root", $mode = 0644, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Hi, I had a working puppet setup using version 0.22 until the ruby security patch bit me. I tried upgrading server and clients to 0.24.1 however my old manifests don''t seem to work anymore. When I run puppetd on the client I see lots of messages like: err: //Node[waterbuck]/yumupdater/Remotefile[/etc/cron.hourly/yumupdater]/File[/etc/cron.hourly/yumupdater]/ensure: change from absent

Hi, I''m exploring Puppet and have hit a rather weird problem. The puppetmaster server is running CentOS4, fully updated, with puppet installed from the dlutter RPM repo, version 0.20.0-1.el4. I tried adding the remotefile function definition from http://reductivelabs.com/projects/puppet/documentation/installation.html in /etc/puppet/manifests/utils/remotefile.pp but when I start

I recently update my remotefile definitions (others might have already done so or have been using a better one than mine). I added an ensure parameter so I could do overrides using remotefile rather than the underlying file: define remotefile($owner = root, $ignore = ".svn", $group = root, $mode = 644, $source, $backup = false, $recurse = false, $ensure = file) { $realsource =

Hi, I''m trying to use several sources to pick from in a remotefile statement: remotefile { "/etc/sudoers": mode => 0440, source => [ "config/apps/sudo/sudoers.${host}", "config/apps/sudo/sudoers" ], sourceselect => first } But it doesn''t seem to work. I get an error like this: "File source

Howdy, Found out about this project while looking for via ONLamp''s FreeBSD build system article. After finding cfengine a tad arcane, this project seems like a good fit for my setup. I''m still at the tinkering phase, but I envision this thing bootstrapping and maintaining several FreeBSD installs which have different CPU''s and packages. The Good News:

So I have $base = "/opt/local/etc" remotefile { "$base/saslauthd.conf": source => "apps/saslauthd/saslauthd.conf", mode => 400, # This file contains special info owner => root; "$base/saslauthd.init": source => "apps/saslauthd/saslauthd.init"; } and

I tried using $name in this manner: remotefile { "/etc/auto_direct.local": mode => 644, source => "solall/$name" } (The remotefile function is handy, BTW) When I use $name here, instead of specifying the actual path to the file (solall/etc/auto_direct.local), puppetd ends up making /etc/auto_direct.local an empty directory. Shouldn''t $name

Hi, I''m banging my head against the usage of variables i defines. Fx. I have this defined to easily create new systemusers: define systemuser($home = $home, $shell = "/bin/bash") { group { $name: ensure => present } user { $name: ensure => present, gid => $name, home => $home, shell =>

Hi, I just upgraded to puppet 0.20.0 today after a short time playing with 0.19.3. The docs say to use the uppercase form for types but that seems to break for me. When I updated the remotefile function to use the new way, the puppet clients complain about objects not being found. For example: ----- OLD WAY (works, just with deprecations) ----- define remotefile (...) { file { $name :

"Service and class definitions are scoped just as variable assignments are." But what about types? Here''s an example: class solserver inherits server { remotefile { "/etc/shadow": mode => 400, group => staff, source => "solall/etc/shadow.server" } Is it possible to just override the "/etc/shadow" definition for

Hello The following chunk is within a class definition. ${name} is being exchanged with an empty string: remotefile { "/${server_xml}": owner => tomcat, group => tomcat, mode => 600, source => "${ftoe_src_prefix_dev}${name}.jvm1" } However in the following chunk, lower down in the same class definition, ${name} is being exchanged

I just upgraded to puppet 0.20.1 from 0.18.4 (both using the debian packages). After the upgrade, I''m getting the following error: err: Could not find type "remotefile" in file /etc/puppet/manifests/classes/kerberos.pp at line 47 Here''s the where the error is occuring: service { nfs-common: ensure => running, hasstatus => true, subscribe

Hi Rowland, Thank you for your reply. Yes, i have tried "net ads user -w HARDWARE -P", but it's still fail. I have add -d10 to llookup the debug mode and got the info below: ads_find_dc: (ldap) looking for realm '' and falling back to domain 'HARDWARE' Opening cache file at /mnt/pool/SYSPOOL/cache/samba/lock/gencache.tdb sitename_fetch: Returning sitename for realm