I’ve installed puppet recently and I’m know trying to understand how it works and make use of it 
If that’s not difficult enough, I encountered this weird behaviour that the –noop argument didn’t do anything. After an hour of searching I realized it was my own stupid fault!
I had to puppet configuration files: /etc/puppet/puppetd.conf (old way) and /etc/puppet/puppet.conf (new way). I browsed throught the source code and it looks like puppet first checks the old file, if it is found it parses that one. If it’s not found, the new file is parsed. I don’t know why, but if the old file is used, the –noop argument isn’t parsed by puppet. So removing /etc/puppet/puppetd.conf was all I had to do. Pffff….
But why did I create the puppetd.conf file? Because I’v read the “Pulling strings with puppet”-book. And althought it’s fairly new, puppet is advancing at a very high rate. So the book is becoming out-of-date already.
2 comments ↓
Hi there! Sorry to hear of your troubles.
Just wanted to mention that if you check page 31 of the book (the paper version) you’ll find that this is discussed. It describes that versions newer than 0.23 look for /etc/puppet/puppet.conf whilst older versions still look for /etc/puppet/binaryname.conf.
Feel free to email me any additional feedback! Thanks for reading!
Hi James! Thanks for the visit!
This kind of stuff is usually my own fault because of not reading it well enough.
Thanks for writing the book! It was very helpful with getting to start with puppet.
Maybe if Puppet gets more widespread it would be nice if someone would write a recipe book for puppet. Just like Rails recipes.
Leave a Comment