-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 10 Sep 2007, schoenfeld / in-medias-res wrote:
I have never used the version prior 0.3 so it appears as if this issue
still exists. The created configuration was created by the current 0.3
version, so if it should not do that, then this needs to be fixed.
That is very strange, I cannot directly see how these entries could end up
in /etc/nss-ldapd.conf otherwise. I will do some further investigation.
[...]
I'm not sure if that helps. Aren't those entries used to specify the
search bases in the ldap directory? I'm pretty sure that the setup will
not work if I just remove them...?!
The options aren't supported in that format. The correct syntax is
specified in the nss-ldapd.conf(5) manual page. It is basically:
base [database] <searchbase>
where the database part can be omitted. If you want to have a different
search base for different databases (e.g. users should only been looked
up under ou=people,dc=some,dc=domain and groups only under
ou=groups,dc=some,dc=domain and not just under dc=some,dc=domain) you can
use the per database search bases.
dpkg-reconfigure should ask you about the global search base and set it
correctly in the config file.
- --
- -- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG5TL1VYan35+NCKcRAoY9AKDDlF/OrJrUtQOFrbNgP404nnqykgCgs6zJ
ZAPnT0bc1nRkDN+MjB64PRo=
=9sLV
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
