RE: large numbers of sockets in CLOSE_WAIT state?
- To: <beacon@dast.nlanr.net>
- Subject: RE: large numbers of sockets in CLOSE_WAIT state?
- From: "Steve Williams" <S.Williams@ukerna.ac.uk>
- Date: Mon, 7 Aug 2006 10:52:54 +0100
- Content-class: urn:content-classes:message
- Content-transfer-encoding: 8bit
- Content-type: text/plain; charset="us-ascii"
- Reply-to: "Steve Williams" <S.Williams@ukerna.ac.uk>
- Sender: owner-beacon@dast.nlanr.net
- Thread-index: Aca35PxXMhaW9CTgSIGLm5wJ+VrjQgCIab1g
- Thread-topic: large numbers of sockets in CLOSE_WAIT state?
> What state was the beacon code distribution in when you applied the
> scaling patch to it? I permuted for a while and got nowhere.
It was a fresh install - no other patches applied - apart from my hacks.
Patch was applied manually (cut and pasted in the appropriate parts) and
worked ok - I do seem to recall disagreeing with something on the +-
side - but I cannot recall what specifically. I think it was reasonably
obvious what was right to do in that place.
> I've thought of that too. If it's going to be maintained long-term,
I
> think that might be the best option....
At the moment it does ASM/SSM and v4/v6 out of the box, so it is a good
start - and due to its popularity in the v6 world there does seem to be
ongoing work on it.
Cheers
Steve