On Fri, Jul 13, 2007, John Yatsko, Jr. wrote:
It didn't appear that it was adding any additional overhead to the box or
lag to users of the proxy, but the cache.log was growing at an alarming
rate.
Doing what I said to the function and recompiling will fix that for you.
It'll run faster as
- Original Message -
From: Adrian Chadd [EMAIL PROTECTED]
To: John Yatsko, Jr. [EMAIL PROTECTED]
Cc: squid-users@squid-cache.org
Sent: Friday, July 13, 2007 7:59 AM
Subject: Re: [squid-users] commSetTcpNoDelay invalid argument
On Fri, Jul 13, 2007, John Yatsko, Jr. wrote:
Red Hat
- Original Message -
From: Adrian Chadd [EMAIL PROTECTED]
To: John Yatsko, Jr. [EMAIL PROTECTED]
Cc: squid-users@squid-cache.org
Sent: Thursday, July 12, 2007 11:40 PM
Subject: Re: [squid-users] commSetTcpNoDelay invalid argument
On Thu, Jul 12, 2007, John Yatsko, Jr. wrote:
I
On Fri, Jul 13, 2007, John Yatsko, Jr. wrote:
Red Hat Linux release 6.0 (Hedwig)
Kernel 2.2.5-15 on an i586
I don't think anyone does Squid development and regression testing on
Linux 2.2.x. Just find the commSetTcpNoDelay() function and do this:
#ifdef TCP_NODELAY
static void
I was running Squid 2.4 for about 5 years. This morning I installed version
2.6 and am now getting this error in my cache.log:
2007/07/12 12:14:06| commSetTcpNoDelay: FD 114: (22) Invalid argument
2007/07/12 12:14:06| commSetTcpNoDelay: FD 141: (22) Invalid argument
2007/07/12 12:14:06|
On Thu, Jul 12, 2007, John Yatsko, Jr. wrote:
I was running Squid 2.4 for about 5 years. This morning I installed version
2.6 and am now getting this error in my cache.log:
2007/07/12 12:14:06| commSetTcpNoDelay: FD 114: (22) Invalid argument
2007/07/12 12:14:06| commSetTcpNoDelay: FD 141:
