No ideas at all?
> -Ursprüngliche Nachricht-
> Von: Bernd Adamowicz
> Gesendet: Dienstag, 11. September 2012 16:16
> An: puppet-users@googlegroups.com
> Betreff: Issue with large directory content
>
> Hi all,
>
> I got this directory configuration:
>
>
> file {
> "${codebase_n
ive scanning everything.
So, the misconfiguration was on my side (nice pitfall), but I wonder if this is
expected behaviour. Shouldn't recursion only be done on the last entry of the
file array? I'm not sure. Maybe the PuppetLabs guys might think about it.
However, thanks again to al
I don't have enough information to say. You might want to run the master and
agent in debug mode to get more output, though.
puppet agent --debug --verbose --no-daemonize
Also, 100 GB? Any particular reason why you're not installing this using a
content distribution system or a large number of
On 13 September 2012 00:12, Christopher Wood wrote:
> I don't have enough information to say. You might want to run the master and
> agent in debug mode to get more output, though.
>
> puppet agent --debug --verbose --no-daemonize
>
> Also, 100 GB? Any particular reason why you're not installing
Thanks for your answers so far.
But beware that the huge artifacts are *not* managed by Puppet (see recurse =>
false). Actually it's a Maven repository filled by Nexus. Only the top
directory is managed by Puppet to have it in place and have correct access
rights. This worked well until I initi
y appreciated!
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Donnerstag, 13. September 2012 10:46
An: puppet-users@googlegroups.com
Betreff: Re: [Puppet Users] AW: Issue with large directory content
Thanks for your answers so
;s a kind of recursive scanning done by Puppet
though 'recurse' is set to false.
Thanks for helping,
Bernd
Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im
Auftrag von Bernd Adamowicz
Gesendet: Donnerstag, 13. September 2012 14:45
An: 'puppet-users@goog
On Thu, Sep 13, 2012 at 8:55 AM, Bernd Adamowicz
wrote:
> For me it still seems there's a kind of recursive scanning done by Puppet
> though 'recurse' is set to false.
This does look like a bug, as you've got a directory with no remote
source, no recursion, and all you want to do is to enforce
. No log output at all.
> Still investigating. But any ideas still highly appreciated!
>
>
>
> Bernd
>
>
>
> *Von:* puppet...@googlegroups.com [mailto:
> puppet...@googlegroups.com ] *Im Auftrag von *Bernd Adamowicz
> *Gesendet:* Donnerstag, 13. September 2012
On Friday, September 14, 2012 6:14:37 AM UTC-5, badamowicz wrote:
>
> The other questions from all of you and finally Den's question, which
> was: "Are you trying to set any permissions inside that directory
> elsewhere in the manifest?" made me rethink everything and pointed me to
> the right
On 09/14/2012 03:09 PM, jcbollinger wrote:
>
>
> On Friday, September 14, 2012 6:14:37 AM UTC-5, badamowicz wrote:
>
> The other questions from all of you and finally Den's question, which
> was: "Are you trying to set any permissions inside that directory
> elsewhere in the manifest?
group => $nexus_group,
> mode=> 0755,
> recurse => false,
> backup => false,
> }
>
> For me it still seems there's a kind of recursive scanning done by Puppet
> though 'recurse' is set to false.
&
*Im Auftrag von *Bernd Adamowicz
*Gesendet:* Donnerstag, 13. September 2012 10:46
*An:* puppet-users@googlegroups.com
*Betreff:* Re: [Puppet Users] AW: Issue with large directory content
Thanks for your answers so far.
But beware that the huge artifacts are *not* managed by Puppet (see
recur
13 matches
Mail list logo
