Path: utzoo!attcan!uunet!husc6!rutgers!bellcore!tness7!texbell!ssbn!bill
From: bill@ssbn.WLK.COM (Bill Kennedy)
Newsgroups: comp.sys.att
Subject: Re: Questions from a new user (SUMMARY)
Keywords: ksh history
Message-ID: <226@ssbn.WLK.COM>
Date: 10 Aug 88 15:33:15 GMT
References: <620@gvgspd.GVG.TEK.COM> <11300001@osiris.cso.uiuc.edu>
Reply-To: bill@ssbn.UUCP (Bill Kennedy)
Distribution: na
Organization: W.L. Kennedy Jr. and Associates, Pipe Creek, TX
Lines: 31

In article <11300001@osiris.cso.uiuc.edu> hood@osiris.cso.uiuc.edu writes:
>
>Come on guys...
>
>A very simple solution to the problem of multiple history files is to
>tack on the process ID to the file name.
>
>	HISTFILE=$HOME/.history$$
>
>Works for me...
>
>Emmet P. Gray				US Army, HQ III Corps & Fort Hood

Once again a tip of the hat to Emmet for a useful and welcome contribution.
I knew there was some way to do it but never read enough to know how.  This
is handy, Thanks!

Not to be a nit picker, but how do you get rid of them when you log out?
If you stay logged in all the time I can see how it works A-OK, but it
looks like it persists after you're gone.  To demonstrate my ignorance,
I can see putting some stuff in /etc/profile that does an ls | grep and
a ps to see if the PID is gone and rm if so, but that seems to be pretty
brute force (I specialize in brute force :-).

It would have to be something like that or when you logged in again, if
you still had a log in active (I mean rm $HOME/.history*) you'd wipe out
one you were still using.  Might this be a candidate for the cleanup
script that clears out /tmp or somesuch?  Just curious...
-- 
Bill Kennedy  usenet      {killer,att,rutgers,sun!daver,uunet!bigtex}!ssbn!bill
              internet    bill@ssbn.WLK.COM