I made a previous chaotic post – sorry – and thought everything was magically in order, but after the configuration of another laptop, I have troubles again… So I’ll try to be the shorter, the clearer here.
My NFS folder won’t mount on my network unless I add the nolock option:
[tcip@tlap:~]$ sudo mount -t nfs /path/to/network/folder /path/to/mount/point
Failed to start rpc-statd.service: Unit rpc-statd.service not found.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
I have installed nfs-utils and services.rpcbind.enable is set to true . I can’t find any relevent option in the configuration file – any idea how to enable it?
hi @rnhmjoj
Thanks a lot for your answer – it works indeed flawlessly as I should have reported (like in my previous post).
However, I need to mount my NFS folders by script, since I’m using a laptop and I am not always at home – else, when not on my network, I will have longer boots for naught, and I don’t know why, but my redshift configuration will not load too in this case .
For now, I will stick to the nolock option, hoping that nobody will mess with the same file at the same time (which should be easily manageable on a private home NAS).