From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 Description of problem: After the network authentication has been selected, autofs should be restarted (made aware of new automounter maps). If this isn't done, users logging in with, for example, NIS accounts won't have home directory mounted. Version-Release number of selected component (if applicable): 1.3.14-1 How reproducible: Always Steps to Reproduce: 1. Install the system 2. Configure NIS authentication with firstboot 3. Try to log in as user Actual Results: Network authenticated account didn't have home directory mounted after the system was configured. Expected Results: Network authenticated account should have home directory after the system is configured. Additional info:
Firstboot calls authconfig-gtk to do the NIS configuration. It seems to me that authconfig-gtk should contain the code to restart autofs if necessary instead of firstboot.
authconfig-gtk restarts automatically all the following services if they exist in /etc/init.d/<service>, --firstboot is its argument and changes are confirmed by pressing OK: firstbootservices = [ "autofs", "dovecot", "messagebus", "postfix", "privoxy", "radiusd", "rstatd", "rusersd", "rwalld", "rwhod", "saslauthd", "sendmail", "smb", "squid", "sshd", "vncserver", "vsftpd", "winbind" ] The autofs is present in the list so I think the problem is somewhere else here ... greetings, Jindrich
Does it also run "nscd -i <blah>" to invalidate the passwd and group caches in a running nscd daemon? I just hit a similar problem where nscd had cached negative entries for users so even after restarting the relevant service (sshd), I could log in. Restarting nscd was necessary.
If restarting nscd is enough to invalidate the caches then yes, it restarts nscd after writing configuration files.
Fixed in FC3.