Comment # 12 on bug 956558 from Neil Brown

(In reply to boo35 boo35 from comment #10)
> (In reply to Neil Brown from comment #8)
> > Is this causing any actual problems apart from the unsightly error message? 
> 
> Well, maybe ...
> 
>   http://lists.opensuse.org/wicked-devel/2015-12/msg00000.html


This looks like it might be the same as bug 947483 ... which you probably
cannot see because it is against SLES12-SP1 rather than opensuse.  But I
believe SLE12 fixes get into Leap, so it should be fixed.... but it looks like
it isn't.

The fix removes references to $remote_fs from /etc/init.d/named and
/etc/init.d/lwresd

> 
> NFS-related dependencies are definitely at issue, between that thread and
> this bug, at least.
> 
> Whether they're related or not, I don't yet know.  I'm poking at it trying
> to figure out what's causal etc.

Yeah, it's complex.  And systemd is new and different and there is a bit of a
learning curve.

systemd doesn't make it at all easy for service execution to be controlled by a
separate config file.  I've managed something, but I'm not sure I like it.

1/ edit /usr/lib/systemd/scripts/nfs-utils_env.sh and add

if [ "$NFS_SECURITY_GSS" == "yes" ]; then
  SVCGSS_PROG=/usr/sbin/rpc.svcgssd
else
  SVCGSS_PROG=/bin/true
fi

somewhere before "mkdir -p /run/sysconfig"

2/ add 
   echo "SVCGSS_PROG=$SVCGSS_PROG"
in the block of similar commands at the end of that file.

3/ create directory /usr/lib/systemd/system/rpc-svcgssd.service.d and create
a file in that directory called "prog.conf" containing

[Service]
ExecStart=
ExecStart=/bin/sh -c "${SVCGSS_PROG} ${SVCGSSDARGS}"

4/ run: systemctl daemon-reload
5/ run: systemctl restart nfs-config.service

Now if you "systemctl restart rpc-svcgss" it should not run the daemon (unless
NFS_SECURITY_GSS is "yes").

I think I'd rather modify rpc-svcgssd in some what... not sure yet.