could have caused the file to get that big?
Regards
Constantin
2015-08-26 16:56 GMT+02:00 Constantin Wolber constantin.wol...@gmail.com:
Hi,
i tried the performance profiler, but it did not really help me figuring
things out.
2015-08-26 14:48:21 + Puppet (debug): Storing state
2015-08
-08-25 18:14 GMT+02:00 kaustubh chaudhari kaustu...@gmail.com:
Hi,
You can run profiler to check who and what is taking time in detail.
https://puppetlabs.com/blog/tune-puppet-performance-profiler
-Kaustubh
On Tuesday, August 25, 2015 at 3:49:28 AM UTC-4, Constantin Wolber wrote:
Hi
Hi,
i searched quite a bit with google but cannot really find an idea of what
to change.
If i do a puppet agent run on a few of my managed servers i get the
following results:
Notice: Finished catalog run in 486.54 seconds
Changes:
Events:
Resources:
Total: 2304
Time:
Hi,
thx a lot for the answer. I was experimenting with the loglevel already
but misunderstood the concept :)
So everything works now as expected.
Once again thx alot
Constantin
Am Donnerstag, 4. September 2014 22:19:02 UTC+2 schrieb Constantin Wolber:
Hi,
i searched quite a bit
Hi,
i searched quite a bit in the documentations and through google but did not
find a suitable solution.
I am using the file resource to change the ownership of a directory
recursively. What happens is that for every single file a notice is
generated for change of user and of group. Since