On tor, 2007-09-13 at 11:24 -0300, Anderson Donda wrote: > Hi list, > > This is my first message here and i have a sample question.. > > Anybody knows how the option "-d <level> " of squid work?.
It's a filter defining how detailed debug messages may be printed on stdout. Normally debug messages only go into cache.log. -d in itself do not enable any extra debugging, just enables them to be printed on stdout if enabled. You define the current debug level using "debug_options" in squid.conf, or toggle full debugging on/off using "squid -k debug". > So, How squid work with each level? You can find the debug sections in doc/debug-sections.txt, and you can set the debug level individually for each section, where level 0 is only critical messages and 9 is full debugging (higher numbers is also supported, but do not increase the amount of debugging shown) When I am debugging Squid I usually use the following command line options: -DNYCd3, and toggle debugging on/off using "squid -k debug" when needed. -d3 usually gives sufficient messages on stdout to understand what is going on when debugging is enabled, and one can always look into cache.log to see all the debug messages. For production use you typically do not use any -d option at all, or perhaps -d0. Regards Henrik
signature.asc
Description: This is a digitally signed message part