Hello Anders, I have the NFS export mounted to /mnt/athlon/ with a link on the KDE-Desktop. I have it set users in fstab so I can mount it from there, which takes a while until it comes up. All other attempts to start Konqueror after that, from a Home link on the Desktop for instance, take very long. K-Panel does not respond until Konqeror comes back.
From console i.e. without even logging into the xserver, the mount takes long, and I get an error "RPC: failed to contact portmap (errno -5)", but the mount is ok and I can move through directories and copy files or directories in both directions normally. BTW: Back a few weeks ago, when I first tried to get this system working I also tried an smb mount, cause I already had the samba server set up for Win clients. It locked up my client system. So did an attempt with cifs, so this has been a long, long ordeal. Not really much fun. On top of that I had to figure out that the orinoco driver isn't stable with the Prism 2.5 wlan card in my laptop, so that I am now using a pcmcia card with the Prism54 module.... Thanks for your suggestions. Chris On Sunday 09 January 2005 11:59, Anders Breindahl wrote: > It sounds very familiar to a problem I couldn't solve, when I was still > using SMB/samba. I would attempt connecting to my server, which would work > fine. However browsing through a directory with a long file list, would > hang the process that was attempting it. > I assume that the mount point of your NFS share is at a place where > Konqueror will look when it comes up. I also assume that your syslog is > rather informationless, as the system would probably time out at some > point. > > If your problem, that makes the system unusable is, that you cannot use > Konqueror on your local machine (and not only on the NFS mount), you could > attempt mounting the NFS share at some other point in the filesystem, so > you don't have to wait for it to come out of the hang. > > Otherwise you would probably need to debug the connection itself. I tried > searching a bit around, and I don't know whether it could be of any help. > > http://sysadminforums.com/t206.html > http://bugs.kde.org/simple_search.cgi?id=nfs+hangs > http://www.wlug.org.nz/NFSNotes > > I am really no expert, but you seem desperate enough for me to attempt > helping. :) > > Regards, Anders Breindahl. > > On Sunday 09 January 2005 11:17, C. Hurschler wrote: > > I've done some reading and tried to figure out how to get name resolution > > working or whether it is even broken. I can ping the server and the > > client (127.0.0.1) itself. I *can* mount the NFS share and everything > > works fine > > in > > > console on the client machine, only Konqueror/KDE hangs. > > > > Can't anyone suggest something, even if combined with a personal insult > > for asking stupid question (I can take it!). I'd really, really like to > > work on this machine, but cant't in it's present state. > > > > Thanks, > > > > Chris > > > > On Friday 07 January 2005 16:47, C. Hurschler wrote: > > > On Friday 07 January 2005 14:49, Kevin Krammer wrote: > > > > On Friday 07 January 2005 14:44, C. Hurschler wrote: > > > > > The problem: in KDE, Konqueror takes a long time (over a minute) > > > > > to start and the KDE-Panel hangs until Konqueror comes up. Once > > Konqueror > > > > > > comes is up I can move through directories in the NFS mount and > > > > > transfer files fine. New instances of Konqeror also take a while to > > > > > come up, both of the NFS mount and of Home. > > > > > > > > Can you check if the system's hostname can be resovled by /etc/hosts? > > > > Preferably by having it as an alias for 127.0.0.1 > > > > > > Sorry, but I don't know what you mean by "can the hostname be resolved > > > by /etc/hosts". > > > > > > I don't have any hosts listed in /ets/hosts on the server, just what > > > was there by default: > > > > > > 127.0.0.1 localhost athlon > > > > > > # The following lines are desirable for IPv6 capable hosts > > > # (added automatically by netbase upgrade) > > > > > > ::1 ip6-localhost ip6-loopback > > > > > > fe00::0 ip6-localnet > > > ff00::0 ip6-mcastprefix > > > ff02::1 ip6-allnodes > > > ff02::2 ip6-allrouters > > > ff02::3 ip6-allhosts > > > > > > on the client I'm using the ip address of the server in fstab for the > > > NFS mount because it couldn't resolve the server hostname otherwise. > > > Is this normal or am I missing something? > > > > > > Thanks, > > > > > > Chris -- C. Hurschler Bodenstedtstr. 13 30173 Hannover
