Peter, Thanks for the explanation.
I hadn't realized that I was abusing the crap out of the autoloader but, now that you explain it, I am! Trevor On Tue, Sep 29, 2009 at 08:28, Peter Meier <[email protected]> wrote: > > nasty side effect from running multiple nodes against the same thread. > If you would run only the wrong manifest against a certain > puppetmasterd thread it would always fail (like trevor suggested the > restart). If puppet would unload all already loaded classes everytime > a new compile request comes in, people would complain puppet being > slow(er). > > So either cache loaded classes and have such nasty side effects. To be > sure that your manifest will always work, simply run it against a very > own puppetmasterd instance. > > Or have a slow(er) puppetmasterd without any caching at all. -> no > "feature" yet. > > Or design by convention and never put more than one class/define into > a file and extensively use puppet's autoloading feature right. ;) > > cheers peter > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
