On Jan 9, 2008, at 11:16 AM, Jesse Becker wrote: > 1) Will --debug include the same information as reported by -- > verbose? Is there any information in --verbose that is not > reported in --debug?
I believe that debug implicitly sets verbose but I may be wrong. I'll check that when I have a chance to crack open the code again. > 2) I've found that when troubleshooting my rules (usually of the > "why didn't this run?" type), the output from --verbose is > insufficient. Usually because I'm trying figure out why a class or > variable has been set (or not). If there's a clean way of > reporting these two things in --verbose mode, that would be > wonderful. (maybe a -vv sort of option?) Well, why not provide an explicit example of how it works today, how you think it should work. I personally am not a particularly imaginative coder. I lose lots of time trying to think over how it "should" work. But once we have consensus on the end result, getting the code changed is easier done than said in most cases. -- Jo Rhett senior geek Silicon Valley Colocation Support Phone: 408-400-0550 _______________________________________________ Bug-cfengine mailing list [email protected] https://cfengine.org/mailman/listinfo/bug-cfengine
