Hi Gordon, > Portmap is required on both the client and server. rpc.statd and > rpc.lockd require it on the client.
Ah, well, that behaviour must have changed. It definitley works on RH 6.2 mounting a share from another 6.2 system: [root@firewall /root]# rpm -q portmap package portmap is not installed [root@firewall /root]# ls /mnt/tmp [root@firewall /root]# mount wc_rh62:/usr/src /mnt/tmp [root@firewall /root]# ls /mnt/tmp Freeswan freeswan-1.6.tar.gz.sig linux-2.2.14-swan redhat , and also on 7.1 (but with some warnings): [root@SBW /root]# rpm -q portmap package portmap is not installed [root@SBW /root]# ls /mnt/tmp [root@SBW /root]# mount wc_rh62:/usr/src /mnt/tmp portmap: server localhost not responding, timed out portmap: server localhost not responding, timed out lockd_up: makesock failed, error=-5 portmap: server localhost not responding, timed out [root@SBW /root]# ls /mnt/tmp Freeswan freeswan-1.6.tar.gz.sig linux-2.2.14-swan redhat So it seems things run cleaner with portmap, but it works without (maybe not with newer NFS servers though). I run portmap on most newer installs, that's why I didn't notice any problems when not using it on more recent systems. Removed it from SBW for this test. Bye, Leonard. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
