Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!blake!ogccse!littlei!uunet!mcvax!ukc!strath-cs!glasgow!jack
From: jack@cs.glasgow.ac.uk (Jack Campin)
Newsgroups: comp.unix.questions
Subject: history file sharing in ksh
Message-ID: <2401@crete.cs.glasgow.ac.uk>
Date: 10 Feb 89 11:05:39 GMT
Organization: Computing Sci, Glasgow Univ, Scotland
Lines: 16

Does anyone know what protocol ksh uses for sharing the history file when
running multiple sessions?  I cannot make sense of what I see happening.  Does
it act differently for shells run from distinct NFS clients than when all
shells are on the same machine?  Is there any concurrency control at all?
(Then again, this is on Suns, and given the dog's breakfast they've served up
for doing locking, it may not be ksh's fault).

Also, is there any way to switch between different history files *within* a
shell?  My motivation - to use /dev/null for a while so sourced-in function
definitions don't clutter up the real one.

-- 
Jack Campin  *  Computing Science Department, Glasgow University, 17 Lilybank
Gardens, Glasgow G12 8QQ, SCOTLAND.    041 339 8855 x6045 wk  041 556 1878 ho
INTERNET: jack%cs.glasgow.ac.uk@nss.cs.ucl.ac.uk    USENET: jack@glasgow.uucp
JANET: jack@uk.ac.glasgow.cs     PLINGnet: ...mcvax!ukc!cs.glasgow.ac.uk!jack