Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
At work, I have a central NFS and NIS server. Normally on weekends I=20 turn off my workstation (HP Integrity IA64 running RHEL 5.1) when I=20 reboot it, and try to log in from the GUI (GNOME), it tells me it can't=20 find my home directory, and sometimes comes up the wrong resolution.=20 However if I restart the GUI by logging off or ctrl-alt-backspace,=20 everything is fine. Additionally, if I log in from my Windows system=20 using putty before I log in from the console, everything is fine.=20 Additionally, if I ssh to any of our 9 systems, the home directories=20 generally come up. The only case where it fails is the first login from=20 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=20 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=20 must enter my password which is authenticated by NIS, where when I log=20 in via ssh (or putty) I use RSA keys in my home directory. In any case,=20 this just seems to be a transient timing issue where there might be a=20 slight delay in the automounting. Once I log in to the initial session=20 (no home directory), I can see that my home directory has been mounted. --=20 Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |