Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

SGI apps Frequently Asked Questions (FAQ)
Section - -26- Why does ksh lock up if one's home directory is NFS- mounted?

( Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Schools ]


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?
See reader questions & answers on this topic! - Help others by sharing your knowledge
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.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:



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 March 27 2014 @ 02:12 PM