Hi Gurus, First of all, my apologies in advance if I am wrong to send this question to this list. Please suggest me the alternate location in that case.
I have a Linux desktop deployment just went live with about 50 Linux desktops all controlled by Redhat FreeIPA(http://www.freeipa.org/) solution for kerberos based centralized login and authentication. Home folder for the users are automatically mounted from one NFS server. All the servers and clients are running RHEL 6.1 and set to KDE desktop by default. All these things work fine except one strange problem. For some reason if the /home/USER_NAME partition becomes inaccessible while she is logged in to KDE desktop, the GUI hangs terribly. I am unable to do anything in GUI at this time and it becomes totally non-responsive. But I can take another terminal(Ctrl+ Alt + F2) and login as root user and do everything. Now to get back to GUI, if I reboot the machine, it takes directly in to the GUI which is in a hung condition and does not give login prompt. I can understand the system hanging while /home partition goes offline suddenly. But what is strange is this condition is resumed after a reboot also. After looking further I could see that during the booting up of the system it is fine and only when kdm is trying to access the NFS home folder, it is hanging. When I take the terminal and look for lsof | grep THAT_USER, I can see several processes initiated by kdm. Is there a way to avoid this ? I suspect kde is trying to initialize the exact setup of previously crashed condition. In the "system settings", I have given to "start a new session" in the session manager. Still it is the same. Is there a way to force kde to NOT initialize anything from the previous session and have an absolutely new session ? Please let me know if you need any further info my side to help me. I would greatly appreciate any suggestion/workaround/fix for this . Thanks indeed and regards, Nasir >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
