3

Setting runinterval=0 in /etc/puppet/puppet.conf causes continuous pulls, not no pulls. I'm trying to arrange puppet so that it will listen for puppetrun calls, but never pull without one.

1
  • What did you do in the end?
    – Industrial
    Mar 17, 2012 at 12:49

2 Answers 2

1

Run puppetd with --no-client option and it will just wait for the master to initiate an update.

From man puppetd:

no-client: Do not create a config client. This will cause the daemon
           to run without ever checking for its configuration automatically,
           and only makes sense when used in conjunction with --listen.
0

Just run puppetd with the --onetime option, and don't start it from init.d or cron.

2
  • This doesn't seem to preserve the ability to use puppetrun from the server to deliver pushes.
    – Zed
    Jan 14, 2010 at 16:47
  • As an additional note, setting runinterval to an absurdly huge number (say, ten years worth) works for preventing pulls after the daemon is running, but a pull will still always be started as the daemon starts. If there's any way to just prevent that initial run, that would probably solve my problem as well.
    – Zed
    Jan 14, 2010 at 16:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.