Roland Mainz writes: > > It sounds like part of a decent RFE to me. > > Ouch... and how would the implementation look like ? The idea was to get > simple access to the data independent of the backend nameservice > details, e.g. a script should not need to implement support for YP, > NIS+, LDAP etc. seperately. Adding those switches would make this MUCH > more painfull to implement since we could no longer use any library > functions and instead have to do our own lookup code in /usr/bin/getent > ... and that's AFAIK an overkill...
Replicating the name service logic itself into getent would indeed be a foolish way to do this. I don't think it'd be as much overkill as it would be bad design. The implementation I was assuming here would most likely include adding interfaces into the name service logic to allow the application to override the nsswitch.conf settings. This obviously has implications for the caching mechanism, but I've always felt that was done at the wrong layer in the architecture anyway. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
