http://bugzilla.suse.com/show_bug.cgi?id=1070013 http://bugzilla.suse.com/show_bug.cgi?id=1070013#c3 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |yast2-maintainers@suse.de Resolution|INVALID |--- Flags| |needinfo?(yast2-maintainers | |@suse.de) --- Comment #3 from Neil Brown <nfbrown@suse.com> --- (In reply to Archie Cobbs from comment #2)

In other words, if I say:

NFS3_SERVER_SUPPORT="no"

then rpc.bind and rpc.statd should automatically be masked (or otherwise prevented from starting) without any additional work.

That can only be done by changes to yast, so they if you use the yast front end to set NFS3_SERVER_SUPPORT to "no", and if it can deduce that nothing else needs rpcbind, then it can run "systemctl mask rpcbind" for you. Let's ask they yast developers what they think.

Put another way, the bug is that the setting NFS3_SERVER_SUPPORT="no" is not fully implemented.

By the way, there should also be a similar setting controlling the enablement of rpc.gssd and rpc-svcgssd, e.g.:

NFS4_GSS_SUPPORT="no"

IF you don't want rpc.gssd, is it sufficient to not have /etc/krb5.keytab. If you want to have the keytab, but not the server (why?) you can explicitly mask rpc-gssd.service. Again, if you want this to happy automatically, yast has to do it for you. It is not possible for you to simply change the sysconfig file and systemd deduce that you don't want certain programs to run. -- You are receiving this mail because: You are on the CC list for the bug.