Hello, Since migrating to OS 11.0, I have difficulties mounting NFS shares as a regular user. I always get the following message: ------------------------<cut>------------------------- pan@kermit:~> mount /website/ mount.nfs: rpc.statd is not running but is required for remote locking. Either use '-o nolock' to keep locks local, or start statd. ------------------------<cut>------------------------- The mounts in question are defined with the 'user' option in /etc/fstab. Looking in /etc/init.d, I found out that: nfs: # statd is started when needed by mount.nfs Just to make sure, I verified and yes, /sbin/mount.nfs is SUID root, so it shouldn't have any problem starting rpc.statd for me. If I first mount the NFS share as root, umount it, then try as a user, it works (because rpc.statd is left running, I suppose), but if I first ty as a user, it fails with the above error message. The same setup worked fine under 10.2. Also, in order to make it work at all, I had to modify the exports on the server and add the 'insecure' flag (because the new client sends the requests from an unprivileged port). Do you know if there is a way to get the client to behave as before ? TIA Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.