On Wed, Dec 07, 2016 at 09:47:29AM +1100, NeilBrown wrote:
> On Wed, Dec 07 2016, J. Bruce Fields wrote:
> > On Fri, Dec 02, 2016 at 02:58:27PM +1100, NeilBrown wrote:
> >> - nfs-config.service is removed, because it isn't really needed with
> >> the above.
> >> - documentation for all the above is provided, including a new
> >> nfs.systemd man page which gives the bigger picture.
> >
> > Still looks pretty good to me.
> >
> > I'm a little worried about user interface churn. We're not done yet
> > explaining that people have to run nfs-config.service after changing
> > things, soon we'll start telling them oh, never mind about that and oh,
> > by the way, you may want to start migrating your configuration to
> > /etc/nfs.conf....
>
> Did we tell people to run nfs-config.server? The intention was that it
> wouldn't be needed. Any systemd transaction that needed nfs
> configuration should run the command once.
>
> Commit: c4940fad2a73 ("systemd: ensure nfs-config service is re-run as needed.")
>
> should have made that happen.
D'oh, I totally forgot that you fixed that, thanks.
> Yes, some migration is needed. I see distros as the primary target for
> that, and the 'include' and '$name' functionality is supposed to allow
> that to be transparent. i.e. the configuration stays as it is, it just
> gets into nfs daemons by a different path.
> If people want to edit /etc/nfs.conf directly, then they are on their
> own, just like people who edited their systemd unit files directly,
> or created replacements in /etc.
Yep, sounds like a plan.
--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
