>>> I'm guessing that it will work if you run it with the -no-deamonize >>> option. >>> >>> You really don't want to use --test. That will have other effects. >> >> Patrick, >> >> could you elaborate on that? > > From the 2.6.1 man page: > > test: Enable the most common options used for testing. > These are +onetime+, +verbose+, +ignorecache, > +no-daemonize+, and +no-usecacheonfailure+. > > >> >> Because --test is what we are using constantly here. I believe it's a >> tip from "Pulling strings with puppet". >> >> From what I gathered, it's the standard way to enforce a run while >> puppet is also running in daemon mode, which is quite exactly what >> Mohammed needs. >> >> So what are the catches to be wary of? > > I would be wary of ignoring your catalog cache. Deploying this throughout the > environment would be detrimental to performance. The individual flags are a > better way to go. >
Ah, misundersting. It is not used for general management. That is done by a plain old daemon process. When a newly changed manifest needs immediate running (e.g. when building a new manifest for a machine or changing something), that is when --test is used here. In such cases, you don't care about the cache, because when the manifest cannot be parsed or the catalogue contains errors, you don't want to apply the original catalogue. You only care to find the source of the errors. Since you put it that way, I think it will be safe for us to stick with --test. Even if the implied options will change, it will still be for testing, which is essentially what I (and Mohamed, I think) am looking for. Thanks, Felix -- 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.
