sandiphw wrote:
Thank you all for valuable assistance. I am working in a corporate
environment. squid is installed on linux server and all these desktops/
laptops (Windows) generating these logs are through samba client. These
thing happens very recently and request are coming from hundreds of
ons 2009-09-16 klockan 06:39 -0700 skrev sandiphw:
Recently I found that logfiles are flooding with informations like
access.log
1253094090.451 0 192.168.42.30 TCP_DENIED/407 1725 OPTIONS
http://ab-desktop/ - NONE/- text/html
Seems that client is running some malfunctioning
ons 2009-09-16 klockan 06:39 -0700 skrev sandiphw:
Logfiles becomes in over a GB witin 7 days and squid stops working. We need
to manually replaced these files with new one. debug_option is set to
default. How to stop these informations comming to logfiles?
It's normal requests and should
Dear sandiphw,
The best option would be to work on the request or misbehaving
application from http://ab-desktop, log-rotation on the squid proxy
works best for me and if you can, please create a syslog server, this
will assist you in ensuring that logs are removed from the production
server and
Thank you all for valuable assistance. I am working in a corporate
environment. squid is installed on linux server and all these desktops/
laptops (Windows) generating these logs are through samba client. These
thing happens very recently and request are coming from hundreds of clients.
We have
I've no ideas about the logging facility. But actually, you can try squid
-k retate with logrotate program.
Regards,
--
Banyan He
Network System Security Infrastructure
Mail: ban...@rootong.com
Blog: http://www.rootong.com/blog
LinkedIn: http://www.linkedin.com/in/banyanhe
Website:
That's some broken clients asking for things without providing the
necessary authentication. There is nothing to do about it,
debug_options doesn't affect access.log .
Your best course of action, if you are in a corporate environment, is
find who is using the PC at address 192.168.42.30,
