Many local connections with Deluge 1.0.0 !

[frilibob]

While using deluge 1.0.0, i see many local connections (ubuntu 8.04) :

Code: Select all

% netstat --inet -n -a | grep 58846
tcp        0      0 127.0.0.1:58846         0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:58846         127.0.0.1:39449         TIME_WAIT  
tcp        0      0 127.0.0.1:58846         127.0.0.1:39450         TIME_WAIT  
[...] 
tcp        0      0 127.0.0.1:58846         127.0.0.1:39521         TIME_WAIT  
tcp        0      0 127.0.0.1:58846         127.0.0.1:39522         TIME_WAIT  
% netstat --inet -n -a | grep 58846 | wc -l
70
%

Daemon local port is 58846 ! It's very very strange !

[danii]

As Deluge now runs as a daemon and a separate ui(web, gtk and console) these connections are the ui and daemon communicating with each other, even if you're using Classic mode, under the hood there is still a daemon and a ui running.

[frilibob]

As Deluge now runs as a daemon and a separate ui(web, gtk and console) these connections are the ui and daemon communicating with each other, even if you're using Classic mode, under the hood there is still a daemon and a ui running.

One (or two or three) socket(s) with status ESTABLISHED to communicate with daemon and each ui, ok !

But 70 sockets with status TIME_WAIT are not normal.

[danii]

I guess it's a bit too much, I had 120 TIME_WAIT at one time, one of the developers will have to say if this is intentional or if this is a bug.

[frilibob]

I guess it's a bit too much, I had 120 TIME_WAIT at one time, one of the developers will have to say if this is intentional or if this is a bug.

Status TIME_WAIT for connections with peers is normal at most. But not for local sockets between daemon and ui...