@Didier: Yes, that's pretty much what I had in mind. Note that "update- rc.d servicename enable|disable" already does all that (upstart override, systemctl enable/disable, etc.), so we should just call that?
> I see the conffiles also have NEED_GSSD, should we handle it in a similar way? An empty value is "auto", and both the upstart job (shell commands in gssd-mounting.conf) and rpc-gssd.service (ConditionPathExists=/etc/krb5.keytab) do that "auto" detection. But indeed we don't currently check this value in the systemd jobs; I wonder if we need to? (e. g. RHEL/Fedora just use these systemd units). I. e. isn't the job of an init system to figure that out for you? Steve, do you have an opinion on this? Do we need the ability to forcefully start gssd without krb, or forcefully suppress it with krb? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428486 Title: Only start rpc.statd if $NEED_STATD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1428486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
