----- Original Message ----- > On 18/01/11 18:12, Nigel Kersten wrote: > > On Tue, Jan 18, 2011 at 8:50 AM, Brice Figureau > > <brice-pup...@daysofwonder.com > > <mailto:brice-pup...@daysofwonder.com>> > > wrote: > > > > On Mon, 2011-01-17 at 18:38 -0800, Nigel Kersten wrote: > > > I'm trying to get a feel for the actual use cases for the > > > Schedule > > > type in Puppet. > > > > Can you elaborate? > > > > > > I've never used them much, people don't talk about them a lot, and I > > want to get a feel for what people use them for :) > > I think this is an under-estimated feature most people don't know > about.
I tend to avoid since things like making sure apt caches are up to date can in some cases be considered critical so I'd rather add a cron job for it rather than rely on a much more complex subsystem to work in order for this important thing to happen. so far whenever I thought I'd use schedule I reconsidered cos the things I wanted to schedule was important, no doubt its sufficient in some cases but thats been my experience. > > > > > > Anyone care to help me out with some real world examples? > > > > I'm using schedules so that my puppetd run "apt-get update" only > > once > > per day. > > > > > > Interesting. How do you deal with pushing out a new repository? > > I'm afraid it never happened, so I never cared :) > But I suppose you can temporarily add a resource override with > schedule > => undef -- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
