I've been looking at using schedules as a way of speeding up Puppet
catalog runs,
but its got one small(ish) annoyance. It would be nice to have the
ability to confirm the
existance of the file on one schedule, while validating the content/
attributes on another -
the idea being that an objects ex
Avi Miller wrote:
> Hey,
>
> Geoff Crompton wrote:
>> How do I use that in other classes and resources? The Language tutorial
>> http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial doesn't
>> mention them.
>
> The TypeReference page does. Check the exec {} type in the example:
>
> exec {
Hey,
Geoff Crompton wrote:
> How do I use that in other classes and resources? The Language tutorial
> http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial doesn't
> mention them.
The TypeReference page does. Check the exec {} type in the example:
exec { "/usr/bin/apt-get update":
sc
James Turnbull wrote:
> Geoff Crompton wrote:
>> Mark Plaksin wrote:
>>> Maybe we're the last to the party but wow do schedules make a huge
>>> difference! Especially with file serving. We added schedules to a few
>>> file-heavy modules and cut the load and hits/day on our file serving
>>> puppe
Geoff Crompton wrote:
> Mark Plaksin wrote:
>> Maybe we're the last to the party but wow do schedules make a huge
>> difference! Especially with file serving. We added schedules to a few
>> file-heavy modules and cut the load and hits/day on our file serving
>> puppetmaster by 2/3. Instead of do
Mark Plaksin wrote:
> Maybe we're the last to the party but wow do schedules make a huge
> difference! Especially with file serving. We added schedules to a few
> file-heavy modules and cut the load and hits/day on our file serving
> puppetmaster by 2/3. Instead of doing everything once an hour
