On Sun, Oct 14, 2007 at 12:10:42PM -0400, Micah Anderson wrote: > * Matthew Palmer <[EMAIL PROTECTED]> [071014 00:07]: > > On Fri, Oct 12, 2007 at 02:47:51PM -0400, Micah Anderson wrote: > > > I dont want those! So I found the pluginsignore config variable, its > > > default is: .svn CVS, which made me wonder why it still pulled them. I > > > tried setting it manually, but that didn't seem to help. > > > > > > Is there another way to set this, and if so, can it be default just like > > > pluginsignore is? > > > > I'm pretty sure pluginsignore is the way to do this, and in fact, in my > > testing (creating a .svn directory by hand inside one of my modules, as well > > as creating a .svn directory in a mocked up plugins tree) works fine. > > Ok... thats odd.
What's really, really odd is that I thought that creating a .svn directory outside of the 'plugins' subdir of my module would amply demonstrate the bug. Now that I've put that directory out a couple of levels, I've got a .svn copy happening. I'll nail this sucker this morning. > On the client: > [EMAIL PROTECTED]:~# cat /etc/puppet/puppet.conf > [main] > logdir=/var/log/puppet > vardir=/var/lib/puppet > rundir=/var/run > ssldir=/var/lib/puppet/ssl > > [puppetmasterd] > templatedir=/var/lib/puppet/templates > > [EMAIL PROTECTED]:~# puppetd -vt --pluginsync Any particular reason you've got a puppetmasterd section on the client, but no puppetd section, and you're specifying pluginsync on the command line? Especially since on the server, you've got: > On the puppetmaster: > > [EMAIL PROTECTED]:/etc/puppet# cat puppet.conf > [main] > logdir=/var/log/puppet > vardir=/var/lib/puppet > rundir=/var/run > templatedir=/etc/puppet/templates > > [puppetd] > pluginsync=true > pluginsignore=.svn > report=true > > [puppetmasterd] > storeconfigs=true > dbadapter=mysql > dbserver=localhost > dbuser=puppet > dbpassword=imnotsendingthisinabugreport > reports=lastcheck A completely different config file. In the middle of a config transition, perhaps? I just ship an identical puppet.conf to all my machines, and it works well. > It somewhat puzzles me that things are going to /var/lib/puppet/lib when > I cant find where that directory is defined anywhere. If you do a 'puppetd --genconfig' on the client, you'll see: plugindest = $libdir And libdir = $vardir/lib And vardir = /var/lib/puppet It all makes sense... eventually. <grin> > I was following > http://reductivelabs.com/trac/puppet/wiki/PluginsInModules which told me > to get rid of the path parameter (check), move my existing plugins out > into modules (check), turn off factsync (check), turn on pluginsync > (check), and point it at the /plugins directory on your puppetmaster > (this I dont really understand) /plugins is now (as of 0.23.2-4) effectively a union of the plugins directories of all of your modules (if you don't specify an explicit path). Hence people can ship custom facts and native types in their modules, which is a big improvement for the usefulness of modules. > Before I tear the last few hairs out of my head, please tell me what I > am missing. You're missing a Puppet package maintainer with Clue, mainly... <sigh> - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
