On Thu, Nov 18, 2010 at 1:45 AM, Nick wrote:
> Hi,
>
> On 18/11/10 03:06, Eric Sorenson wrote:
>> Note I also changed your 'recurse => true' to 'recurse => remote', a sadly
>> under-documented feature which eases recursive copies by recursing the source
>> directory to build a list of files that n
Hi,
On 18/11/10 03:06, Eric Sorenson wrote:
> Note I also changed your 'recurse => true' to 'recurse => remote', a sadly
> under-documented feature which eases recursive copies by recursing the source
> directory to build a list of files that need checksumming, not the target.
> (see http://projec
On Nov 17, 2010, at 2:48 PM, Russell Fulton wrote:
>
> (note to developers: please 'rescue' this error and provide something
> meaningful to the user ;)
Someone else posted a fix.
On the subject of the error itself, this bug is known and fixed in 2.6.x and
0.25.5. If you want more info, loo
On Nov 17, 2010, at 2:48 PM, Russell Fulton wrote:
>source => '/home/sensors/Rules/raw',
This needs to be a puppet:// url which matches up to an appropriate 'mount' in
your server's /etc/puppet/fileserver.conf:
# fileserver.conf
[sensors]
path = /home/sensors
allow = *
# end f
Hi Folks
I'm a relative newbie to puppet (been playing about a month)...
I am trying to push out a directory containing a bunch of files to a number of
machines and thought I could do this using the recurse attribute:
file {
"/home/snort/Rules/raw":
mode=> "750",