On Wed, Dec 2, 2009 at 8:22 AM, R.I.Pienaar <[email protected]> wrote: > > > > ext/puppetlisten/puppetlisten.rb > > > --------------------------------- > > > comment from the top of the file reads: # this is a daemon which > > accepts > > > non standard (within puppet normal intervals) puppet configuration > > run > > > request. I'm unsure why one would use the puppetlist/puppetrun > > scripts? > > > Wouldn't you just run puppetd in daemon mode and use the 'real' > > > pupperun? > > > > There was a reason for this - Luke will know. > > > > > ext/puppetlisten/puppetrun.rb > > > ----------------------------- > > > comment from the top reads: # this scripts calls a client and ask > > him to > > > trigger a puppetd run uses # SSL for communication based on the > > puppet > > > infrastructure the client # allows access based on the > > > namespaceauth. same question as the previous one above in the > > > puppetlisten.rb section > > > > Ditto. > > I think these are from ohadlevy, its a light daemon that kicks your > puppetd, it for people who run from cron but who also want the puppetrun > equivelant. > > true - thats a daemon which uses puppet SSL and namespaceauth infrastructure to trigger puppet runs when puppet is not running as a daemon. I've written it mostly as a proof of concepts how to reuse puppet certificates (without loading webrick and all of the memory hungry parts) and to avoid the huge memory problems i had with puppetd (300-500MB of resident ram).
useful, though mcollective is better :P > :) -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
