[Bug 994212] Re: ldap fails to start when /etc/network/interfaces not used
Well, fact is, that the autofs daemon is started right before network
manager is bringing (wired) interfaces up:
snip
Jul 8 12:39:07 myclient automount[1431]: Starting automounter version 5.0.6,
master map ou=auto.master,ou=[...],dc=example,dc=org
Jul 8 12:39:07 myclient automount[1431]: using kernel protocol version 5.02
Jul 8 12:39:07 myclient automount[1431]: lookup(file): file map
/etc/ou=auto.master,ou=[...],dc=example,dc=org missing or not readable
Jul 8 12:39:07 myclient automount[1431]: no mounts in table
[...]
Jul 8 12:39:09 myclient NetworkManager[1100]: info Auto-activating
connection 'Kabelnetzwerkverbindung 1'.
[...]
Jul 8 12:39:10 myclient NetworkManager[1100]: info Activation (eth0)
successful, device activated.
/snip
An elegant workaround would be to use a NetworkManager dispatcher script.
Create a new empty file and make it executable:
touch /etc/NetworkManager/dispatcher.d/80automount
chmod 755 /etc/NetworkManager/dispatcher.d/80automount
Now you can open this file and paste your script which, in its simplest
form, restarts the autofs daemon:
snip
#!/bin/bash
# These arguments are handed over by NetworkManager
INTERFACE=$1
ACTION=$2
case $2 in
up)
# Restart the automount daemon
/etc/init.d/autofs restart
;;
down)
;;
pre-up)
;;
post-down)
;;
*)
echo $Usage: $0 {up|down|pre-up|post-down}
exit 1
esac
/snip
Save, exit and restart. Automount should be working now.
What it does: As soon as a new network connection is brought up successfully,
the autofs daemon is restarted. Since at this point the connection is up
already, it is now able to get the correct LDAP automount maps from the LDAP
server.
This script can be improved of course, but you get the idea.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/994212
Title:
ldap fails to start when /etc/network/interfaces not used
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/994212/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd
Confirmed for Precise beta. Please, for the sake of corporate and government customers (where LDAP and/or Kerberos is very likely to be deployed), elevate the priority of this bug. I gather that this is of not much interest for the majority of private desktop users, but in more professional environments, this is a showstopper, meaning that such distribution simply cannot be deployed in our corporate networks. -- 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/423252 Title: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/423252/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 728047] Re: smbd + ldap hangs at startup after update
Vanilla install on Lucid 10..04.3 here, still the same issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/728047 Title: smbd + ldap hangs at startup after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/728047/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 445619] Re: [karmic] slapd should start before kerberos kdc and admin servers, possibly others
Hmm, this problem is still present in Lucid. One can easily change the order manually though, e.g: update-rc.d -f krb5-admin-server remove update-rc.d -f krb5-kdc remove update-rc.d krb5-admin-server start 20 2 3 4 5 . stop 18 0 1 6 . update-rc.d krb5-kdc start 20 2 3 4 5 . stop 18 0 1 6 . -- [karmic] slapd should start before kerberos kdc and admin servers, possibly others https://bugs.launchpad.net/bugs/445619 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 423252] Re: NSS using LDAP on Karmic breaks 'su' and 'sudo'
I agree. gnutls is often the source of strange, unforseen errors. I'd also vote to replace it with the reliable and proven openssl. So linking libldap2 with openssl fixes this issue? -- NSS using LDAP on Karmic breaks 'su' and 'sudo' https://bugs.launchpad.net/bugs/423252 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 442498] Re: karmic openldap cut-to-bone-and-beyond install, why ????
I've just written another HowTo that I'll gladly throw into the mix: http://ubuntuforums.org/showthread.php?t=1313472 By the way: it is really a shame that there is no official word from canonical on this. Not even an official tutorial on how to deal with the new situation. It's nice that canonical is slowly seeing the importance of an LDAP-based (heck, even Kerberos-based) network infrastructure, but this whole situation should have been handled more carefully. -- karmic openldap cut-to-bone-and-beyond install, why https://bugs.launchpad.net/bugs/442498 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint network-authentication] Make Ubuntu authenticate against Network Authentication services
Blueprint changed by Ro: Whiteboard changed to: Updated spec URL, added in the text from UDS 2007-01-31 kamion: Approved (as it stands, it's relatively simple), but you're going to have to get a move on! authtool doesn't seem to have made any progress since September, and Samba 3.0.24 hasn't been released yet which may prove to be a blocker. Please keep me updated. Also, is the 30 days time estimate still accurate? 2007-02-31 svg: as laptops are becoming ubiquitious, it would be important to make configuration as such that som form of caching is involved (ldap cache, sync to local passwd, ..?) such that user is able to log in when not connected to the corporate network 2009-04-30 ro: @svg: LDAP Cached Credentials solves these problems in a quite elegant manner. So no problem here. -- Make Ubuntu authenticate against Network Authentication services https://blueprints.launchpad.net/ubuntu/+spec/network-authentication -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
