Any Squid gurus out there?

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I've installed Squid on one of my boxes at home, but am having a problem with logging.

I know the box is proxying requests properly - I've configured a browser with the IP address of the box and the port I'm running Squid on (default, port 312. The cache is filling up and, if I check out the cache.log file I can see oodles of things being cached.

However, there isn't a single entry in the access.log logfile. I'm not running any authentication, but my understanding is that proxy accesses should still be logged regardless - is this not correct? I'd rather not have to piss around setting up an authentication mechanism when all I really want to do is log all web browsing activity on my LAN - I think my wife would get the hump if I started asking her to authenticate to a proxy server - it'd be too much like being at work for her

I've checked every newsgroup I can find and the only mention of a similar problem is from someone who has installed Squid on a Linux box and obviously not given the correct permissions on the directory that the access.log file resides in.

Help!

Cheers

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Bit of lemon juice and a touch of chopped chilli?

 

I find fried with noodles better.

Other than that i have no idea!

 

I was running squid some years ago - but it was on a NetBSD box - so I'm not sure I am going to be much help!

Harry.

 

Cheers Harry - I figured it out in the end. The access log parameter in the config file was enclosed in quotes and shouldn't have been.

All sorted now - now I can get down to ACLs and blocking!