>> ~/.nfs000000160000351200000001 in the first account home, I am able to >> login using the first account. OK. I understand that the content of ~/.nfs000000160000351200000001 should be basically the same as the original ~/.bash_history which has been deleted in the NFS server via the second server. Right? The strange thing is: when I try to login the first sever with a different login session, why the login session still hangs on this nonexistent ~/.bash_history. Is it that NFS remembers ~/.bash_history as just ~/.nfs000000160000351200000001. Unless the last program that uses ~/.bash_history quit, all subsequent programs trying to access ~/.bash_history will actually get to ~/.nfs000000160000351200000001? >> Can anybody pinpoint the cause of the problem given the above description? > > That's expected behavior, see: http://nfs.sourceforge.net/#faq_d2 -- Regards, Peng -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
