On Wed, 19 May 2010 16:28:08 +0200, Simon Brereton <simon.brereton@xxxxxxxx> wrote: >> From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] >> Sent: Monday, May 17, 2010 9:59 PM > > >> >> Well, there you go. Debug level #2 is full of debugging traces. >> >> >> >> FWIW: >> >> level 0 - critical failure messages. >> >> level 1 - warnings and important notices >> >> level 2 thru 9 - debug traces (section specific) >> >> >> >> This is why the recommended level is 1 and not 2 or higher. >> > >> > Amos >> > >> > I'll try that - but there are too things to note.. >> > >> > 1) I initially increased the debugging to see the auth failures - >> which >> I >> > couldn't see - despite going to 9. In fact, I saw no difference >> > between >> 1 >> > and 2 so that's why I left it at that. >> > >> > 2) My logging options are to output to: >> > 1128 access_log /var/log/squid3/access.log combined >> > 1137 cache_log /var/log/squid3/cache.log >> > >> > >> > I meant to send this out on Friday. Anacron doesn't seem to have >> sent >> me >> > the notice since I made the change, but nonetheless, I'm curious as >> to >> why >> > that would make a difference. My assumption is that no matter what >> I >> put >> > the debugging level at, it should log to file, not to anacron. >> >> They are part of the configuration file loading. The system log is >> used for initial startup messages before the cache.log file is >> configured for use. debug_options takes effect immediately on being >> read in, but cache.log opening is done after the config load is >> finished and the final cache.log location is known (it can currently >> be specific twice or more with different filenames). > > That would imply that squid is also being restarted on a daily basis.. Is > that implication correct? Is that behaviour correct? > Yes, it does appears so. Behaviour correctness depends on what is being done at the time of restart. The only "normal" operation which is done daily by external processes is log rotation. That should be using "squid -k rotate". However, there may be other opeartions somewhere in your setup that mean a full restart is required. Amos
