-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Previous versions (before 0.3) tried to use the existing nss_ldap
configuration file (/etc/libnss-ldap.conf) directly as a basis for a new
nss-ldapd configuration file (/etc/nss-ldapd.conf).
With release 0.3 nss-ldapd now does full checking of the configfile
(errors out on invalid lines instead of silently ignore those lines). On
any new installs a small and simple configfile should be installed instead
(looking in the nss_ldap file for deafaults). Existing configurations are
however not touched.
You could fix your situation by manualy removing the nss_base_* entries
from /etc/nss-ldapd.conf (and any other lines that are not recognized) or
moving the file aside and running
dpkg-reconfigure libnss-ldapd
to configure it again.
If you use one of the more "advanced" features (like SSL, Kerberos,
attribute mapping or custom filters) you may ocasionally encouter upgrade
issues. This should stabilize a bit in coming releases.
- --
- -- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG5SfuVYan35+NCKcRAu8EAKDjhaafMvskTM1uTgEKpGPBrSVcRwCfWe31
3J+pgfbrlvEbzvhJ8gl8QS4=
=dVEt
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
