socket freeze (?) on nix
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

socket freeze (?) on nix

Started by ATAG, 25 September, 2008, 16:08:16

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ATAG

Hi!

I have a big problem about nix version. "Keep slow client online" is turned off. However when a client becomes "slow" and hub quits its nick it doesn't close the socket. The client see he is online, but receives nothing anymore from the hub.

here is an example, i hope you will understand this
Client:
Quote[2008-09-24 19:54] <[HUN]acidcode> M? ERIKA MIVAN?
[2008-09-24 20:22] *** Sz?tkapcsolva (disconnected)
[2008-09-24 20:22] *** Kapcsol?d?s diablohub.hu:4111... (connecting to..)

And this is from the hub:
Quote[19:38:56] <[HUN]acidcode> M? ERIKA MIVAN?:D
[19:39:13] <[HUN]Erika83> gyors ?sszev?gdosom magam le?blitem ?s itt is vok:D
[19:39:23] <[HUN]Erika83> Danci gyere ki a hora :D
....
[19:50:40] <VALKNUT> Kil?p:[?M??al?]GhostGirl? -> now hub quits her nick but she keep see herself online...

Just watch the timestamps... Our clock are synchronized!!! This happend with me too, its not a client side error..

ATAG

#1
I don't know.
I received the $Quit @ 19:50, she received a message 4 minutes later!!! (19:54) (and 16 minutes later then the message was sent (19:38)).
Really intresting :-/

PPK

I'm checked that, and improved disconnect when user is slow 8) Socket was closed, but it tryed to send rest of data in send buffer before that.. and if user was too slow he was not able to receive them and maybe he don't receive close too ::)
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

SMF spam blocked by CleanTalk