search for: pluginsignor

I''m working with a pretty simple config at the moment to track down some issues I''m seeing with custom facts and plugins. I have factsync = true (default locations) and I have a simple fact in /var/lib/puppet/facts/ (actually it''s David''s netmask plugin) my pp file I''m testing with contains only: notice "netmask: ${netmask}" puppet -v

...sr/share/puppet/modules name = apply node_name = cert node_name_fact = "" node_name_value = vusion-production node_terminus = plain noop = false onetime = false passfile = /var/lib/puppet/ssl/private/password path = none pidfile = /var/run/puppet/apply.pid plugindest = /var/lib/puppet/lib pluginsignore = .svn CVS .git pluginsource = puppet://puppet/plugins pluginsync = true postrun_command = /etc/puppet/etckeeper-commit-post preferred_serialization_format = pson prerun_command = /etc/puppet/etckeeper-commit-pre privatedir = /var/lib/puppet/ssl/private privatekeydir = /var/lib/puppet/ssl/private_...

...s the password for its private key. # Generally unused. # The default value is ''$privatedir/password''. passfile = /etc/puppet/ssl/private/password # What files to ignore when pulling down plugins. # The default value is ''.svn CVS .git''. # pluginsignore = .svn CVS .git # Run the configuration once, rather than as a long-running # daemon. This is useful for interactively running puppetd. # onetime = false # Where individual hosts store and look for their private key. # The default value is ''$privatekeydir/$certname.p...

For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction