Comment # 3 on bug 1166680 from William Brown

Right, I see the problem.

What I deployed:

passwd: compat kanidm
group:  compat kanidm
shadow: compat kanidm

hosts:      files mdns_minimal [NOTFOUND=return] dns
networks:    files dns

services:    files
protocols:    files
rpc:        files
ethers:        files
netmasks:    files
netgroup:    files nis
publickey:    files

bootparams:    files
automount:    files nis
aliases:    files

What's on a "clean install"

passwd:        compat
group:        compat
shadow:        compat
# Allow initgroups to default to the setting for group.
# initgroups:    compat

hosts:      files dns
networks:    files dns

aliases:    files usrfiles
ethers:        files usrfiles
gshadow:    files usrfiles
netgroup:    files nis
protocols:    files usrfiles
publickey:    files
rpc:        files usrfiles
services:    files usrfiles

automount:    files nis
bootparams:    files
netmasks:    files


I think that it's going to happen that people absolutely will deploy their "as
is" configs like I did, and they'll trip up over this issue. It's probably fine
to ask me to "fix" this to usrfiles, but I think realistically that the
solution should be that the "files" module should be updated to route these
requests between /etc/services and /usr/etc/services instead, rather than rely
on nsswitch here.