Argh. But puppet client daemon will be running in the noop mode, so none of
this will work. My bad.
On Fri, Sep 10, 2010 at 3:24 PM, mohit chawla wrote:
> Ugh, never mind the nick/name.
>
> So, one way I can think of doing is to put the puppet client's controlling
> module, in a run stage that's
Ugh, never mind the nick/name.
So, one way I can think of doing is to put the puppet client's controlling
module, in a run stage that's executed before main, which will restart
puppet and toggle the noop value.
On Fri, Sep 10, 2010 at 3:08 PM, mohit chawla wrote:
> Any suggestions, folks ?
>
>
Any suggestions, folks ?
On Wed, Sep 8, 2010 at 1:35 PM, alcy wrote:
> Hi,
>
> I wanted to have my puppet client daemons running in the noop=true
> mode, and changes could be triggered centrally through puppetrun --
> noop false. Also it would be nice in an inverse situation, when client
> daemo
Hi,
I wanted to have my puppet client daemons running in the noop=true
mode, and changes could be triggered centrally through puppetrun --
noop false. Also it would be nice in an inverse situation, when client
daemons are running in the default (noop = false) mode and before
testing out a new(smal
