Red Hat Bugzilla – Bug 133035
authconfig fails to properly enable NIS authentification
Last modified: 2007-11-30 17:10:49 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install fresh sytem in NIS network where auto.master and auto.home
2. follow firstboot and enable NIS authentification.
3. login to X
"you home directory /home/xxxxx is not available....."
authconfig does good job starting pormapper and ypbind. however autofs
needs to be restarted after ypbind is launched to pick up NIS
I suspect that autofs needs to be restarted when any changes are made
to pick up new maps from for example LDAP.
Any other services needs to be restarted?
I know about this bug and I'm not quite sure if it is a failure of
firstboot or authconfig. I assume you used authconfig-gtk.py called
from firstboot? In that case autofs won't be restarted when autofs is
not running at the time authconfig is executed (authconfig-gtk.py uses
Have you autofs running at the time the NIS authentizationis enabled
Can you please write me if the same problem occurs when you use
text-mode authconfig to startup NIS authentication?
autofs will not run after fresh install because "no mount point
configured". authconfig text or gtk mode will have to (re) start
autofs if NIS (or any other authentification which potentially can
provide new mount points) is turned on so autofs has a chance to query
new map and find its new mount points if configured.
likewise if NIS is shut down autofs may have to be restarted as well
to refresh its map list.