It sounds like the problem is source port exhaustion, for the outgoing sessions
that squid creates.
Why do you consider the TIME_WAIT as such to be a problem? There is no
significant problem to have some hundreds of thousand
TIME_WAIT sockets on a server port.
Wouldn't there be a 65,536
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 26, 2008 5:11 AM
To: S.KOBAYASHI
Cc: 'Squid Users'
Subject: Re: [squid-users] I want to purge too many TIME_WAITs
immediatelyafter closing HTTP port.
mån 2008-02-25 klockan 17:59 +0900 skrev S.KOBAYASHI:
Hello there,
I have a bit
: 'Squid Users'
Subject: Re: [squid-users] I want to purge too many TIME_WAITs
immediatelyafter closing HTTP port.
mån 2008-02-25 klockan 17:59 +0900 skrev S.KOBAYASHI:
Hello there,
I have a bit problem while majoring the squid performance now.
There are many TIME_WAIT connections left
: [squid-users] I want to purge too many TIME_WAITs
immediatelyafter closing HTTP port.
mån 2008-02-25 klockan 17:59 +0900 skrev S.KOBAYASHI:
Hello there,
I have a bit problem while majoring the squid performance now.
There are many TIME_WAIT connections left on the squid port
