Linux Mint Forums

Version 1.2.2 worked fine - no problems with a nfs-mount.
The latest version - 1.2.3 - gives an error when starting rpc.statd - which means you need some acrobatics (-o nolock) in order to nfs-mount.
I guess the ultimate culprit may be sm_notify as attempting a nfs-mount I get a message that the '-p' option is invalid (apart from the fact that rpc.statd is not running ...

The required NFS setups exist, such as /var/lib/nfs
http://linux.about.com/library/cmd/blcm ... .statd.htm
https://bbs.archlinux.org/viewtopic.php?id=100427
https://help.ubuntu.com/community/SettingUpNFSHowTo

Those links, a few places I would look at for information..
--not trying to be funny here!.

• It is always best to review the setup whenever there is any error or failure

Unless any setup should be different from v1.2.2 (of which I have seen no documentation) - no, nothing has been changed on my side.
During the recent update, I watched it 'closing down statd', 'enabling stat' and then 'starting statd' - which then gave an error.
It has worked perfectly for me from the very first lmde and up to this last update (and some other distros as well).
And fyi - 'bleeding edge' archlinux still uses v1.2.2

As to the actual arguments passed to rpc.statd, I have no idea as it is started well beyond my control - its started as part of the boot-process because the nfs-mount has been activated.

As I said - I was _watching_ the sucker being updated and returning an error upon restart.

It's an issue with portmap, apparently. There's a small discussion about it in the thread LMDE Breakages 'read here first'.

Rather than re-type info. on the fix, I'll link that part of the thread:
http://forums.linuxmint.com/viewtopic.p ... 83#p405948

thanks CiaW.
Todays upgrade did it - a new version of nfs-common

I'm surprised that nobody else reacted to it - am I the only one using nsf-mounts?