-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hmm...perhaps both modes could be supported.
Have one way to schedule and another to run inline.
That would be quite useful.
Trevor
On 04/08/2010 01:45 PM, Thomas Bellman wrote:
> Dan Bode wrote:
>
>> I would prefer if puppet ran the sync. It woul
Patrick wrote:
On Apr 8, 2010, at 2:15 AM, Thomas Bellman wrote:
This does two things: when run the first time, it actually does
an rsync of a directory tree. And then it creates a cron job
for keeping the tree synchronized with the source. You use the
'creates' parameter to indicate a file
On Thu, Apr 8, 2010 at 10:50 AM, Paul Lathrop wrote:
> On Thu, Apr 8, 2010 at 10:45 AM, Thomas Bellman
> wrote:
> > Dan Bode wrote:
> >
> >> I would prefer if puppet ran the sync. It would be nice to receive
> puppet
> >> events for any changes made via rsync (essentially reports of which
> files
On Thu, Apr 8, 2010 at 10:45 AM, Thomas Bellman wrote:
> Dan Bode wrote:
>
>> I would prefer if puppet ran the sync. It would be nice to receive puppet
>> events for any changes made via rsync (essentially reports of which files
>> change, this would require that it is implemented in ruby).
>>
>>
Dan Bode wrote:
I would prefer if puppet ran the sync. It would be nice to receive
puppet events for any changes made via rsync (essentially reports of
which files change, this would require that it is implemented in ruby).
I can see from reading the man page that there is a --dryrun call tha
On Apr 8, 2010, at 2:15 AM, Thomas Bellman wrote:
> Trevor Vaughan wrote:
>
>> Mainly sugar around the call with the ability to twiddle all of the
>> useful rsync flags in a platform-agnostic manner where possible.
>> That would be truly awesome.
>
> I have such a define in my module "nsc-puppe
That's definitely reasonable and probably worthwhile.
And having this be an internal puppet type that could parse the output
of rsync and report errors, etc... would be ideal.
Trevor
On Thu, Apr 8, 2010 at 6:22 AM, Dan Bode wrote:
>
>
> On Thu, Apr 8, 2010 at 2:15 AM, Thomas Bellman wrote:
>>
On Thu, Apr 8, 2010 at 2:15 AM, Thomas Bellman wrote:
> Trevor Vaughan wrote:
>
> Mainly sugar around the call with the ability to twiddle all of the
>> useful rsync flags in a platform-agnostic manner where possible.
>>
>> That would be truly awesome.
>>
>
> I have such a define in my module "n
Trevor Vaughan wrote:
Mainly sugar around the call with the ability to twiddle all of the
useful rsync flags in a platform-agnostic manner where possible.
That would be truly awesome.
I have such a define in my module "nsc-puppet-utils" (available at
http://www.nsc.liu.se/~bellman/nsc-puppet-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd +1000 this.
Mainly sugar around the call with the ability to twiddle all of the
useful rsync flags in a platform-agnostic manner where possible.
That would be truly awesome.
Also, the ability to natively wrap this in SSL with something like
stun
On Wed, Apr 7, 2010 at 8:20 PM, Christopher Johnston wrote:
> Nfs is not always feasible in controlled environments. I run kernels with
> the nfs stack completely removed to cut out kernel bloat (for size).
>
And it can be slow and annoying, yes :)
> Rsync integration into puppet directly would
Nfs is not always feasible in controlled environments. I run kernels
with the nfs stack completely removed to cut out kernel bloat (for
size).
Rsync integration into puppet directly would be attractive and very
useful.
Sent from my iPhone
On Apr 7, 2010, at 8:07 PM, Michael DeHaan
wr
On Wed, Apr 7, 2010 at 1:38 PM, Patrick wrote:
> I second this. Puppet will load the whole file into ram, and puppet never
> deallocates memory. It's almost always better to move big files by putting
> them into a package or using an "Exec" type with "creates."
>
>
Just to be clear, the deall
I second this. Puppet will load the whole file into ram, and puppet never
deallocates memory. It's almost always better to move big files by putting
them into a package or using an "Exec" type with "creates."
On Apr 7, 2010, at 10:21 AM, Daniel Kerwin wrote:
> Not sure about a limit but pupp
Not sure about a limit but puppet isn't very good at transfering
really big files. This may lead to memory problems afaik
On Wed, Apr 7, 2010 at 6:56 PM, Seeker wrote:
> Hi all, Just wondering, is there a limit on the file size that you can
> transfer with PUPPET.
>
> Thank you all
>
> --
> You r
Hi all, Just wondering, is there a limit on the file size that you can
transfer with PUPPET.
Thank you all
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from t
16 matches
Mail list logo
