Hide Forgot
We use LDAP to configure our automounts, but the automounts aren't being set up properly. no automount map are available. if i launch the command just after boot systemctl restart autofs.service then the maps are available. i have tried to had NETWORWAIT=yes in /etc/sysconfig/network as i did in F13 but it didn't solve the problems. it s like autofs is started before ldap was available.
That probably means that the autofs init scripts needs ordering dependencies after ldap in the LSB header. Reassigning to autofs.
(In reply to comment #1) > That probably means that the autofs init scripts needs ordering dependencies > after ldap in the LSB header. Reassigning to autofs. Symptom is the same in Fedora 16. Our home directories are automounted. Graphical login is rejected for ldap authenticated users, due to no home directory. Log in at a console, restart autofs. Then, home directory is mounted for the user upon login. Is there a workaround equivalent in systemd for NETWORKWAIT=yes in /etc/sysconfig/network? Thanks, Craig
This probably should be marked as a duplicate of 756123 since that bug contains my comments as to what we could do to deal with the problem.
Ian, I have just read 756123 and 709637. I understand the issue much better, now. Surprisingly, systemctl enable NetworkManager-wait-online.service worked for me. The automount maps are now working and the home directory is available at login. Graphical login and console login are working correctly. Our centos-5 ldap server is on the same subnet as the clients. I have 10 linux servers and 6 linux desktops using autofs. We have a mixture of centos and fedora, all fedora 14 or earlier. The fedora 16 client is a new installation on a laptop. I will look forward to Fedora 17 and improved function with autofs. Thank you for your time, Craig
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping