On Sat, Mar 22, 2008 at 04:15:16PM +0100, Joerg Sonnenberger wrote: | On Sat, Mar 22, 2008 at 11:35:37PM +1100, Tyler Retzlaff wrote: | > If an nsswitch module source were to be added to tree where should it live? | > /usr/lib/libc/nsswitch/nss_xxx has been suggested is there a better / more | > appropriate place? | | /lib/nsswitch and /usr/lib/nsswitch as default location? I think Tyler was asking about the source location, not the run-time destination, although his original question wasn't frame correctly. (Just based on a prior conversation we'd had) We have prior art for src/lib/i18n_module, so I suggest src/lib/nss_module. FYI: the run-time modules are presently searched for in the `standard dlopen() search path', which is generally /usr/lib (default) or /lib:/usr/lib (for /bin and /sbin). | > /etc/nss_xxx.conf | > /etc/nssiwtch.d/nss_xxx.conf | | /etc/nsswitch.d/ seems preferable to me. I wouldn't do the dance with a | single config file if no reason for compatibility exists. libc should | provide modules with a function to determine the path name of the config | file though. /etc/nsswitch.d/<modulename>.conf, without the leading "nss_" ? Thus, /etc/nsswitch.d/ldap.conf for /lib/nss_ldap.so.0 For example, /etc/nsswitch.d/dns.conf could contain a superset merge of /etc/resolv.conf and /etc/hesiod.conf, if we chose to do that. Luke.
Attachment:
pgpFvJNHki7Xs.pgp
Description: PGP signature