On 01.04.2011 20:29, Oliver Hookins wrote:
On Apr 1, 4:45 pm, David Schmitt<[email protected]> wrote:
On 31.03.2011 23:32, Trevor Vaughan wrote:
Fair enough.
nss:<foo> or nss_foo?
According to nsswitch.conf(5) this would include:
aliases
ethers
group -> Covered by 'group' type
hosts -> Covered by 'host' type
netgroup
networks
passwd -> Covered by 'user' type
protocols
publickey
rpc
services -> The one we want to cover
shadow -> Covered by 'user' type
So, if this logic holds, would we need to rename/alias the 'host' type
to nss_host?
It's not a horrible idea so long as it's a full version deprecation.
It would add consistency and tell you more concretely what you're
actually configuring. For instance, if some crazy person decides to
create a full BIND type then you would have another 'host' scope in
there.
"Well, actually"[1] nss can talk to ldap, nis, files, berkley dbs, and a
bunch of other nasty stuff, and complex combinations of them. So
"nss_user" would have have a very local meaning, depending on the
contents of nsswitch and the user you're looking at. I'm all for having
support for any and all of those mechanisms, I'm just not sure that they
should all be managed via nss_user providers...
Best Regards, David
[1]http://tirania.org/blog/archive/2011/Feb-17.html
Nigel's point notwithstanding, I'd suggest nss_files since we are
talking specifically about that interface of the name service. Perhaps
hosts can be deprecated in favour of nss_hosts but yes, again this is
getting very GNU libc-centric.
What system does OSX and the BSDs use when talking about these files?
I suspect for many of them there is no equivalent whatsoever on
Windows so as much as cross-platform support may be desirable it may
not even be possible.
Windows does have hosts, lmhosts, networks, protocol and services files
in C:\Windows\System32\drivers\etc ; on my system they only contain the
most very basics, that is IANA registrations, and localhost.
Best Regards, David
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
