Thanks for that change. Cheers. Cédric
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1016592
Title:
libnss-ldap should not depend on libpam-ldap
To manage notifications about
Public bug reported:
On Ubuntu 12.04, libnss-ldap (264-2.2ubuntu2) should not depend on
libpam-ldap (via ldap-auth-config and ldap-auth-client).
Currently, if one installs libnss-ldap, libpam-ldap also gets installed
through dependencies.
Installing LDAP name services does not - should not,
Thanks for your answer.
We actually have install-recommends disabled in /etc/apt/apt.conf.d
If you look closely, you will see that libnss-lap depends on ldap-auth-
config, which in turn depends on ldap-auth-client, which in turn depends
on libpam-ldap (thus the indirect dependency).
Debian has
The problem is the same for NIS:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/119660
I do agree that porting autofs to upstart would be ideal. Unfortunately,
it seems it requires a good knowledge of Ubuntu's upstart events chain
to do it properly. Maybe someone knowledgeable enough with
After a few reboot, it seems I found the quick-'n-elegant fix for that
issue:
r...@lucid-golden:~ # cat /etc/init/autofs-ldap.conf
# Restart AutoFS-LDAP after everything has settled
start on (stopped networking and stopped rc RUNLEVEL=[2345])
exec /etc/init.d/autofs restart
Problem with
I'm experiencing the (same?) problem with Lucid (and autofs-ldap).
After rebooting, one time it works... another time not (until autofs is
manually restarted)
That does sound like an upstart race condition.
Unfortunately, this is quite important for enterprise environments :-(
I guess at the time
