Roland Mainz wrote:

>No, because in the case that the matching entries in /etc/nsswitch.conf
>contain more than "files" you need nameservice-specific calls, one for
>YP, one for NIS, one for NIS+, one for LDAP etc. - and you would have to
>care about the lookup order and fallback behaviour if a nameservice is
>down etc. etc. ...
>... that's why I was thinking to extend /usr/bin/getent to include these
>items if they are not available via other ways.
>  
>

I still don't understand your original question:

>> Is there a nameservice-independent way to obtain the values for
>> "user_attr" and "publickey" from a shell script
>

I got - and still get - confused by what you mean with
"nameservice-independent way".
You agreed (above), that nsswitch.conf is parsed and processed (in the
well defined order, from left to right).

So how would you be able to bypass any nameservice defined in
nsswitch.conf, getting those "user_attr" attributes in a
"nameservice-independent way"?
I mean, either you get it locally (files), or you may get it via one of
the nameservices (its commands).
What do you mean?

Do you intend to intrude somewhere ;-)


_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to