[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Single Page
Top Document: SGI apps Frequently Asked Questions (FAQ)
Previous Document: -25- How can I tell application X about my screen size?
Next Document: -27- Why can't I 'talk' to Suns?
-
Search the FAQ Archives
Single Page
Top Document: SGI apps Frequently Asked Questions (FAQ)
Previous Document: -25- How can I tell application X about my screen size?
Next Document: -27- Why can't I 'talk' to Suns?
-26- Why does ksh lock up if one's home directory is NFS- mounted?
Date: 15 Oct 1995 00:00:01 EST ksh(1) uses a single ~/.sh_history file for all of a given user's ksh processes, so must be able to lock that file. Locking is robust for local files but not over NFS. Install patch 547 (or its successor) to fix some known NFS bugs and be sure lockd is 'chkconfig'ed on and rpc.lockd and rpc.statd are actually running. If all else fails, set the HISTFILE environment variable to a file on a local disk.
Top Document: SGI apps Frequently Asked Questions (FAQ)
Previous Document: -25- How can I tell application X about my screen size?
Next Document: -27- Why can't I 'talk' to Suns?
Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
sgi-faq@viz.tamu.edu (The SGI FAQ group)
Last Update October 22 2009 @ 05:34 AM