Hey,
today I noticed lots of sockets (>300) in TIME_WAIT state on my systemimager
server. Since all sockets were associated with bittorrent, I investigated a
bit and found the following parameter to btlaunchmany to be the cause:
--rerequest_interval 1
According to the documentation this means that the bittorrent seeder on the
image-server will ask for new peers every second. Since a new socket is
created each time and the default socket timeout (at least on debian) is
several minutes, this will result in many sockets in TIME_WAIT mode. Another
side effect is that the bittorrent-tracker.log will gets very big.
Granted, these are more annoyances than problems, but I was wondering if
this small interval is even needed for systemimager server.
IIRC the bittorrent seeder running on the image-server will register himself
at the tracker, so that the tracker can give other clients the ip of the
image server. For these other clients a small interval may be good, so that
they are informed early when new sources are available. However, since the
peer running on the image server is only a seeder and doesn't need clients
to download from, I don't think this is needed. Or am I missing something?
Also keep in mind that the default interval is 5 minutes(!).
I changed the interval on my server to the default of 5 minutes and I will
see in a few days if the imaging still works.
Thanks,
Thomas Krause
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
