From: david s. <rock808@DavidSlimp.com> - 2002-12-27 01:08:59
|
well, I can't say for sure what your specific problem might involve, but I can say that from my experience, what you are describing IS indeed an NFS problem.... I don't run Gtkg all the time from my laptop, but when I am working from home i have my laptop hooked up to my LAN which provides some NFS shares. I have found that if I unplug the ethernet cable when I take it on the road and then try to do simple commands like 'du', 'ls', etc, the terminal window that those commands were run in hangs. After a period of several minutes I notice my CPU usage meter steadily increase and finally i cannot run any commands from any window, nor can i log in to a new session, and eventually have to reboot. I would suggest you try the same thing with your computer... not running Gtkg, and disconnecting your ether cable after establishing a NFS share... and see if you get the same results. My guess is that you will, and hopefully should show you that this is not something CAUSED by Gtkg, but rather Gtkg does also fall victim to this NFS problem. david On Wed, Dec 25, 2002 at 04:20:07AM +0100, Christian Biere wrote: > Rap...@po... (Raphael Manfredi) wrote: > > > Quoting joe...@bl... from ml.softs.gtk-gnutella.users: > > Then it's a network/NFS problem. GTKG uses *blocking* read() system > > calls to get at your file's data. That would explain why it freezes. > > It's not just a NFS problem. I've just added a bunch of small files and > clicked the "Rescan" button. The GUI stalled for (very) many seconds and > I don't share anything from a NFS mounted device. As the SHA1 > calculation is already a background job, maybe it could be rearranged to > allow non-blocking read()s. > > Christian -- David Slimp rock808@DavidSlimp.com http://www.DavidSlimp.com Yahoo Instant Messenger ID: rock808 |