[Bug 1428486] Re: Only start rpc.statd if $NEED_STATD

[Didier Roche]

rather than preventing the user being able to systemct enable/disable,
we have that option to follow that path:

1. patch to remove the Wants= in nfs-server.service and add an [Install] section to both rpc-statd.service and rpc-statd-notify.service with:
WantedBy=nfs-server.service
2. and doing the one time enablement (and sedding the config file as we did for others) + shipping an upstart override if not disabled

That way users would have the systemd tooling to enable/disable the
service and we use the same thing for the one time
enablement/disablement.

Making sense?

PS: I see the conffiles also have NEE_GSSD, should we handle it in a
similar way?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1428486

Title:
  Only start rpc.statd if $NEED_STATD

Status in nfs-utils package in Ubuntu:
  Triaged

Bug description:
  A remaining TODO item from the systemdification (bug 1312976) was to
  only start rpc.statd if /etc/default/nfs-common enables NEED_STATD=.
  This is a bit awkward with systemd and we generally avoid/move away
  from such "enable the unit" config files as they are redundant with
  update-rc.d enable/disable and systemctl enable/disable (which is the
  canonical way to enable/disable a unit).

  We should probably just add a comment pointing to systemctl
  enable/disable, and make sure that this works as intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1428486/+subscriptions