Re: large numbers of sockets in CLOSE_WAIT state?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steve Williams wrote:
>> 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.
Ok - I was thinking of doing it that way, but I hadn't got around to it.
>
>> 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.
Fair enough. I might run both on different groups, and see what the
users want... One thing I don't like is that dbeacon has limited
functionality on Solaris, and a Solaris box is all I have easily
available at the moment.
Thanks for the input...
--eli
>
> Cheers
>
> Steve
>
>
- --
Eli Dart Office: (510) 486-5629
ESnet Network Engineering Group Fax: (510) 486-6712
Lawrence Berkeley National Laboratory
PGP Key fingerprint = C970 F8D3 CFDD 8FFF 5486 343A 2D31 4478 5F82 B2B3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFE14qzLTFEeF+CsrMRAqJdAJ4m9yNzK7ZH6upDkSeKNdL+Rl2iigCfb5AT
LtSM1y08etC74yR3g2QoGYE=
=k23a
-----END PGP SIGNATURE-----