[Pkg-utopia-maintainers] Bug#370569: Dbus and ldap

[Tim Dijkstra]

On Mon, 28 Aug 2006 14:21:10 +0200
sjoerd at spring.luon.net (Sjoerd Simons) wrote:

> Hi,
> 
>   All of you reported bugs with ldap users and dbus. As i mentioned in some
>   bugreports already, i have some problems with the new libnss-ldap and logging
>   in on some of my machine when nscd is not running (nothing specific wrt to
>   dbus). 

Something similar here. With libnss-ldap enabled the machine seems to
wait indefinitely for some respons of the ldap server at some point
during the boot. The soft-locking-on-boot trick didn't help.

>   Recently someone noted on the bugreport to libnss-ldap about this (#376426)
>   that disabling tls solved these issues. Could you guys let me know if: 
>     (0) TLS is enabled in your libnss-ldap config 
>     (1) If disabling it (swithing from ldaps:// to ldap:// in 
>         /etc/libnss-ldap.conf) solve the dbus issues your seeing?
> 
>   Note that it is important to switch of nscd during these tests. If the
>   answers to both questions is yes, then the dbus issues are a side-effect of
>   #376426. In that case the dbus bugs should be reassigned to libnss-ldap. 

No, I don't use ldaps, so I doubt it has anything to do with that. 

As a work around for the problems with the recent libnss-ldap, I made
some custom init scripts to change the contents of nsswitch.conf not to
mention ldap until after the boot process is over. I then also
discovered that I need to restart dbus after the network is running (and
the nsswitch.conf is back to the orignal state.) for ldap-users to be
able use it. So it seems that dbus somehow ignores the new nsswitch.conf
until it is restarted. The rest of the system works normal btw.

I probably should have mentioned this in the bug report earlier... 

I do have a good work around for the bug now, but I still think dbus
should notice the new nsswitch.conf (which would AFAIK go automatically
if it would use the normal getuid() calls).

grts Tim