I think changing the nsswitch.conf order is a really intrusive change
that can't be done without a discussion.

But what I meant to say was that enabling the files domain without
changing the nsswitch.conf order currently doesn't bring any benefit.
This will change in future versions when we add a better API to control
the local users, but at the moment, it is OK to disable the files domain
at ./configure time.

I'm sorry this was not mentioned more prominently in the 1.16 release
notes.

Reply via email to