-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks Matus for the DiskD issue on FreeBSD. One more thing, we have a couple of FreeBSD squid servers. We have both Squid-2.5 and Squid-2.6 running. We do load-balancing among the squid servers by using an Alteon load-balancer. My problem is that I see alot of invalid request in my cache.log from this Alteon load-balancer. Below are the some part of the cache.log details: Please note: x.x.x.x is a real static public IP. On my Server with Squid-2.6 it shows as: clientReadRequest: FD 290 (x.x.x.x:7856) Invalid Request parseHttpRequest: Unsupported method 'aa clientReadRequest: FD 290 (x.x.x.x:7856) Invalid Request parseHttpRequest: Unsupported method 'aa On my Servers with Squid-2.5, it shows as: 2006/11/09 14:28:38| clientReadRequest: FD 119 Invalid Request 2006/11/09 14:28:40| parseHttpRequest: Unsupported method 'aa Only difference with Squid-2.5 and Squid-2.6 is that the real IP of the Alteon gets shown as shown above. In all my squid servers, cache.log shows this type of requests from the Alteon load-balancer once every second. In one day, I can expect to see at least 86400 entries of this type in my cache.log on each of my squid servers. Please shed some light on these issue. On Thu, 9 Nov 2006 09:05:13 +0100 Matus UHLAR - fantomas <uhlar@xxxxxxxxxxx> wrote: > On 08.11.06 22:48, Tek Bahadur Limbu wrote: > > I am using squid-2.5/2.6 with FreeBSD 6.0/6.1 on some of my Dell > > SC420/430 servers with 1GB memory. I need to compile DISKD support > > in FreeBSD kernel. I read in Squid's FAQ which recommends the > > following values for the message queues and shared memory: > > if you have FreeBSD5 or higher, you can use aufs, which should be > faster and doesn't require SHM tuning. > - -- With best regards and good wishes, Yours sincerely, Tek Bahadur Limbu Jwl Systems Department Worldlink Communications Pvt. Ltd. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFUuw3wXBzLfFnNxQRAovxAJ9JGhXLRUXjKNNh2/TdXJfccNb1fwCgj15G 12BeAbTwsgx5f+7YV/hRuyE= =yzsU -----END PGP SIGNATURE-----
