I am experiencing the same problem under Windows 2000 Advanced Server. Freenet 0.2 Release will leave connections in CLOSE_WAIT until the OS eventually runs out of sockets. My work-around has been to restart the Freenet server ever few days.
--Lucky Green <shamrock at cypherpunks.to> "Among the many misdeeds of British rule in India, history will look upon the Act depriving a whole nation of arms as the blackest." - Mohandas K. Gandhi, An Autobiography, pg 446 http://www.citizensofamerica.org/missing.ram > -----Original Message----- > From: freenet-dev-admin at lists.sourceforge.net > [mailto:freenet-dev-admin at lists.sourceforge.net]On Behalf Of Michel > Bouissou > Sent: Wednesday, May 31, 2000 01:11 > To: freenet-dev at lists.sourceforge.net > Subject: [Freenet-dev] Freenet forgets closing connections > > > Hello, > > See that: > > [root at mycomputer freenet]# netstat | grep 19114 > tcp 0 0 mycomputer.mydomain:4113 TK152079.tuwien.t:19114 > CLOSE_WAIT > tcp 0 0 mycomputer.mydomain:4098 TK152079.tuwien.t:19114 > CLOSE_WAIT > tcp 0 0 mycomputer.mydomain:19114 cx103627-a.santab1:4361 > CLOSE_WAIT > > Well, these 3 connections have remained in the CLOSE_WAIT status > for about 3 > days now. > > Guess Freenet is forgetting to do a little housekeeping ;-) > > Regards. > > Michel. > > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev > _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
