sorry, maybe i didn't make that clear: X is a tcp/ip beast. problems in X often are a precursor of network layer problem in a kernel release. just thought you should be informed about that is all.
cheers jon > > Jon wrote: > > > see earlier comment about redhat. > > gnome taking out x and then leaking sounds like a problem beginning in the > network layer. > > Well, I won't compare an unknown Gnome / X weird problem with my present > Freenet issue. > > Please note the following anyway: > > 1) My server looks really healthy, indeed, and has an uptime of a month or so. > It serves a lot of processes without ever any problem. It's a production > machine, rather stable. There's no X nor no Gnome running on it ;-) > > 2) Killing the Freenet server process immediately released the 3 hung > "CLOSE_WAIT" tcp connections that had stayed hung for 3 days. They immediately > disappeared from netstat. > > 3) Killing the Freenet server process also freed immediately 9 megabytes from > my .freenet data storage directory (???). It was not any recent or ongoing > data transfer, as my server wasn't processing any Freenet insert or request at > the time I killed it, and hadn't been for a while. > > 4) Restarting the Freener server then works plain good. But maybe some sockets > may hang again in the future? > > Go figure... > > 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
