similar to: subscribed files sourced from puppet fileserver

Following patch for pfile.rb and pfile/source.rb allows the user to set a replace => false parameter on a file sourced by puppet, but not replaced if checksums do not match. This is for cases in which it is desired to distribute initial "bootstrap" files and ensure future existence, yet allow them to be modified on the node. RTS --- pfile.rb~ Wed Aug 2 04:47:05 2006 +++ pfile.rb

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

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

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

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

Has the component/type defaults syntax changed for 0.22.x? I have a component: <snip> define remotefile($owner=root, $group=root, $mode, $source, $backup=false, $recurse=false, $groupname="default") { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

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:

<a href="http://www.joyent.com">Joyent</a> and <a href="http:// www.sun.com">Sun</a> are proud to present the first in a series of Hack Days, where you will get a chance to hear about the latest technologies and learn how to use them in an interactive unconference styled event. The first Hack Day launches on August 8th at the Axis Cafe in San

There is serious memory leak bug in ferret. I''m having this error on TextDrive Container (aka. Joyent Accelerators) OpenSolaris with Ferret 0.11.4 It happens while searching for some terms with accented or special characters. This makes ferret to allocate lots of memory (usually reaching 3+ GB) and failing if another query like this is executed. Any ideas on that, could this be locale

I'm setting up a postfix server using "The Book of Postfix". In ch 15 there is a section on testing saslauthd which I can't get to work. I can get it to work using shadow password authentication, but it fails on pam. I don't kow squat about troubleshooting pam. Any PAM wizzes out there that can help? I saw a unrelated post talking about something needing to be in the pam

On Wed, Sep 11, 2019 at 01:34:27PM +1000, Jobst Schmalenbach wrote: > CentOS 7.X, sendmail.x86_64 8.14.7-5.el7, cyrus-sasl.x86_64 2.1.26-23.el7 > > There are conflicting message on how to increase the logging of saslauthd. > > I know I can do this: > /usr/sbin/saslauthd -d -n0 -m /var/run/saslauthd -a pam > > but that requires a terminal as saslauthd logs the output

Hello, I'm having trouble to get saslauthd running on a centos-5.3. I can't autheticate via testsaslauthd. Here's what I do using a fresh /etc/sasldb2: 1) start saslauthd in debug mode: saslauthd -d -a shadow -O /usr/lib64/sasl2/smtpd.conf -r -l 2) saslpasswd2 -c -a mail -u mail testuser 3) testsaslauthd -u testomat -p <mypassword> -s smtp -r mail shell output of

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

Hi users of EL6 based distributions, I'm pleased to announce a new alternative binary package repository for EL6 x86_64. The aim is to provide a supplemental set of packages which may contain software not included in your base system. These packages are based on pkgsrc, a cross-platform package manager. In this initial release there are 13,152 packages available. For now I am specifically

Hi, I am trying to configure dovecot/postfix with virtual users and sasl auth but there are so many tutorials with mistakes and subtle differences that at the end I am lost. So I am running Ubuntu server 11.04 (natty) and when I installed my server I had followed the following guide http://workaround.org/ispmail/etch Then I have migrated to dovecot 2.1 and now I am trying to allow

Hello I''m wondering if anyone has looked into adding pkgsrc package management as a provider for Package? We use Joyent accelerators (zones on OpenSolaris) for our many of our production services and about a year ago Joyent switched from Blastwave to pkgsrc for userland packages. pkgsrc catalog - http://pkgsrc.se/ pkgsrc guide - http://www.netbsd.org/docs/pkgsrc/ joyent pkgsrc

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

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.