On Jan 23, 2011, at 5:58 PM, eshamow wrote: > I can tell you that for me, and for my group, it's a halfway step > between reloading Puppet and watching the logs, and a full --debug -- > no-daemonize run. > > So for instance, when they're troubleshooting a bug in a newly-written > or modified class, I suggest a puppetd -tv run to just output the > errors and successes...and if you see an error, you could then follow > up with the more verbose --debug to get at what Puppet was trying to > do that generated it, provided that you didn't get enough from the > former. > > It might be wise to consider combining a bunch of similar options > (verbose, test, debug, etc) into a "verbose" with levels of output -- > either v1, v2, v3 or vv, vvv, vvvv, etc.
Just for clarification, "--test" isn't a level of messages. It just causes "--verbose" to be added. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
