Automount and /home

[j.natowitz-KealBaEQdz4 at public.gmane.org (Jerry Natowitz)]

According to the nfs(5) man page, retry=n is supported for nfs mounts in 
Linux.

	Jerry Natowitz
	j.natowitz-KealBaEQdz4 at public.gmane.org


Jerry Feldman wrote:
> AFAIK, the retry parameter is not supported in Linux, at least according 
> to the man pages. This morning for some reason the login screen would 
> not display on my monitor (this was related to the KVM), so I logged in 
> via putty, and the login requested a password which means the /home/gaf 
> directory was not mounted, but after authenticating, I was logged into 
> my home directory. The issue is strictly a timing issue where the 
> mounting of the home directory occurs after the initial login request. 
> So, I think the issue may be more in the login process rather than an 
> issue with automount per se.
> 
> On 05/25/2009 10:41 AM, Jerry Natowitz wrote:
>> I remember having a similar problem on Solaris.  The solution was to 
>> add "retry=3" to the auto_home line(s) in /etc/auto_master on the 
>> server.  I don't exactly what conditions required this, only that it 
>> worked.
>>
>>     Jerry Natowitz
>>     j.natowitz-KealBaEQdz4 at public.gmane.org
>>
>>
>> Jerry Feldman wrote:
>>> At work, I have a central NFS and NIS server. Normally on weekends I 
>>> turn off my workstation (HP Integrity IA64 running RHEL 5.1) when I 
>>> reboot it, and try to log in from the GUI (GNOME), it tells me it 
>>> can't find my home directory, and sometimes comes up the wrong 
>>> resolution. However if I restart the GUI by logging off or 
>>> ctrl-alt-backspace, everything is fine. Additionally, if I log in 
>>> from my Windows system using putty before I log in from the console, 
>>> everything is fine. Additionally, if I ssh to any of our 9 systems, 
>>> the home directories generally come up. The only case where it fails 
>>> is the first login from the GDM login screen initially after boot. It 
>>> is a minor pain. Note that my network is run through 2 GB Netgear 
>>> switches, 1 switch connects the firewall, and the office connectors, 
>>> and the other one is located in the rack where the 8 servers are 
>>> located. It's possible that the propagation delay could be part of 
>>> the issue, but that would not explain why ssh via putty works. One 
>>> other bit of info is that when logging in via GDM, I must enter my 
>>> password which is authenticated by NIS, where when I log in via ssh 
>>> (or putty) I use RSA keys in my home directory. In any case, this 
>>> just seems to be a transient timing issue where there might be a 
>>> slight delay in the automounting. Once I log in to the initial 
>>> session (no home directory), I can see that my home directory has 
>>> been mounted.
>>>
>>>
>>
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Discuss mailing list
> Discuss-mNDKBlG2WHs at public.gmane.org
> http://lists.blu.org/mailman/listinfo/discuss