[Arthur de Jong] > This has been implemented in the 0.6.4 release. Great.
> Having a hostname of localhost will probably result in problems. If > you want to look into how it's implemented have a look at > nslcd/cfg.c:cfg_getdomainname(). What is basically does is look up > the hostname and uses that to look up the canonical name which > should be a FQDN. I do not understand why you do it like this. It seem to be the wrong algorithm. I would expect it to only use the DNS config and ignore the current hostname. If resolv.conf have search sub.top.com top.com I would expect it to first look for _ldap._tcp.sub.top.com and then for _ldap._tcp.top.com, independent of the hosts current name and DNS entry. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
