linuxdcpp-team team mailing list archive

[poy <837544@xxxxxxxxxxxxxxxxxx>]

since ADCH++ now listens for both ip4 & ip6 connections (rev 508), and
DC++ connects to both simultaneously, 2 client entities are created at
the same time when a client connects.

one of them goes through the regular login process; the other stays in
limbo and gets disconnected later on thanks to the "LogTimeout" feature.
therefore, while slightly obnoxious, this shouldn't prevent high hub
uptimes as long as useless client entities are being properly cleaned
up.

i see the following oddities, but i could be wrong:
- DC++ should disconnect unfruitful connections when one of them successfully connects.
- ADCH++ shouldn't create a new client entity when the same client has already connected via a different socket. this assumes it would be possible to compare an ip4 address to an ip6 one...

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/837544

Title:
  Handles trapped on closing socket

Status in ADCH++:
  New

Bug description:
  Rev 519 tryed on both XP and Win2k8 server

  When a user logs out not all handles are freed (on logon it creates 3
  handles , also a bit strange) and when the socket is closed only 2 of
  them are freed resulting in a core that is notgoing to run long.

  This bug existed before untill poy changed the way the socket was
  closed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/837544/+subscriptions