Comment # 16 on bug 990356 from jc sl

(In reply to Neil Brown from comment #13)
> Argg....
> Could you please edit
>   /usr/lib/systemd/scripts/nfs-utils_env.sh 
> and change the one instance of VERSION_PARAMS (all uppercase) to
> version_params (all lower case)
> 
> While you are there, if there is still a "version_parms" somewhere (missing
> 'a'), change it to "version_params" as well.
> 
> That shold cause the /run/sysconfig file to be correct, and then NFSv2 and
> NFSv3 won't be enabled.

Hi.

There was one instance of both VERSION_PARAMS and version_parms. One fixed
there are two modified lines in /run/sysconfig/nfs-utils. I add the values of
the changed variables before and after the edition:

   # Before
   RPCMOUNTDARGS=  
   RPCNFSDARGS=  --nfs-version 4 --nfs-version 4.1  4

   # After
   RPCMOUNTDARGS=  --no-nfs-version 2 --no-nfs-version 3 --nfs-version 4
--nfs-version 4.1
   RPCNFSDARGS= --no-nfs-version 2 --no-nfs-version 3 --nfs-version 4
--nfs-version 4.1  4

Now the system boots correctly with rpcbind.socket masked. However it takes its
time, more than 7 minutes (that is about 5 minutes more than the usual boot
time). It seems that NFSv2/3 locking still wants to be started:

   ...
            Starting NFS status monitor for NFSv2/3 locking...
            Starting NFS mount daemon...
   ...
   [  OK  ] Started NFS mount daemon
   [FAILED] Failed to start NFS status monitor for NFSv2/3 locking..
   See 'systemctl status rpc-statd.service' for details
            Starting NFS server and services...
   ...
   [ **** ] A start job is running for NFS server and services (xxx / no limit)
   ...

Greetings.