Hello,
I store camera pictures in a git repository, which became quite big:
104 GB for the whole (non-bare) repository.
I wanted to fix the files permissions, and thought puppet might be the
good tool for this (I like its declarative way of simplifying my
life).
I gave it a try, with the following statements
node "navi" {
file {
"/Users/seb/Pictures/pictures/":
mode => 0640,
owner => "seb",
group => "staff",
recurse => true,
ignore => ".git"
}
file {
"/Users/seb/Pictures/pictures/.encfs5/":
mode => 0600,
owner => "seb",
group => "staff",
recurse => true,
}
file {
"/Users/seb/Pictures/pictures/.git/":
mode => 0600,
owner => "seb",
group => "staff",
recurse => true,
}
file {
"/Users/seb/Pictures/pictures/.git/hooks/":
mode => 0700,
owner => "seb",
group => "staff",
recurse => true,
}
}
And a call to "sudo puppet -l /tmp/puppet.log ~/statement.pp"
Well, that was 4 hours ago and since then, ruby is eating 100% of my CPU
(of one core of my 2.26GHz core 2 duo).
From the log file, I can tell that puppet is indeed fixing perms, at a
rate lower than one file per 10 seconds.
I think find, xargs and chmod would take a few minutes at most (will try
later).
Why is puppet so slow at this job? Is there any way I could improve the
speed?
Thanks for any insight.
--
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 this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
