This *might* work:
package { $packages: ensure => installed }
But you might have to do this:
define do_stuff {
package { $name: ensure => installed }
}
do_stuff { $packages: }
Trevor
On Wed, Apr 8, 2009 at 18:39, engle wrote:
>
> I am having troubles finding the proper documentation that
I have finally figured out a way to do this, posting in case anyone else has
the same question. I defined my 'default' schedule and just included it in the
class everything else inherits from. This may not be the best way, but it
works for me.
schedule { normal:
range=> "17:00
+1 to Paul's comments. I like having the daemon and if you really want
it the cron option is easy to configure. I'm intending to show both
in the 2nd edition of the Puppet book.
Regards
James Turnbull
On 10/04/2009, at 11:43 AM, Paul Lathrop wrote:
>
> On Thu, Apr 9, 2009 at 11:03 AM, Ky
On Wed, Apr 08, 2009 at 07:44:07PM +0100, Gary Law wrote:
> 2009/4/6 Marcin Owsiany
>
> >
> > On Mon, Apr 06, 2009 at 10:50:17AM +0100, Gary Law wrote:
> > > + start-stop-daemon --stop --quiet --pidfile /var/run/puppet/puppetd.pid
> > [...]
> > > g...@dv01:~ $ ps -ef | grep [p]uppet
> > > root
UK here - I would say 500 - 800GBP/day
I think puppet is one of those implementations where a consultant/trainer
can be highly effective from day one (results can be fast and highly
visible), so could be seen as good value for money.
2009/4/10 Larry Ludwig
>
> > I also think consultancy at go
On Fri, Apr 10, 2009 at 9:51 AM, David Lutterkort wrote:
>
> On Thu, 2009-04-09 at 10:44 +1000, Karl Bowden wrote:
>> I've only been learning enough ruby for two days just to test the
>> augeas bindings, so mind the quality.
>
> Kudos to you :)
>
>> Attached is a bindings demo that shows how the b
