I'm seeing this error in cache.log when restarting squid:
storeSwapMetaUnpack: insane length (-663045478)!
My understanding is that it's complaining about a URL length and the
weird value seems to indicate the store has been corrupted? Is there a
way to fix this without clearing the entire cache?
hello all,
I currently get some sun v210 boxes running solaris 8 and
squid-2.6.12
and samba 3.0.20b I will upgrade these proxies into 2.7.4/3.0.32
next
monday but before doing this I would like to ask you your advices
and/or
experiences with tuning these kind of boxes.
the service is
... but when watching the protocol analyzer I see ...
IMHO these days Ethernet eavesdropping really isn't much of an issue (despite
conventional wisdom:-). Much more dangerous are spyware/trojan keyloggers;
server penetration is annother danger.
Eavesdropping on all network traffic from
IMHO these days Ethernet eavesdropping really isn't much of
an issue (despite conventional wisdom:-). Much more dangerous
are spyware/trojan keyloggers; server penetration is annother danger.
Eavesdropping on all network traffic from any connection used
to be a big problem when network hubs
Hi,
I run squid in an ISP scenario. We have got two identically configured
squid caches being load balanced among 4,000 users over a 50 Mbps link. The
system runs quite well, although not without the occassional hiccups. But,
there is a complain from users about not being able to access
Hi,
I run squid in an ISP scenario. We have got two identically configured
squid caches being load balanced among 4,000 users over a 50 Mbps link.
The
system runs quite well, although not without the occassional hiccups.
But,
there is a complain from users about not being able to access
