Path: utzoo!utgpu!attcan!uunet!husc6!spdcc!gnosys!gst From: gst@gnosys.UUCP (Gary S. Trujillo) Newsgroups: comp.sys.att Subject: Re: Questions from a new user (SUMMARY) Summary: but how about all the extra shells? Keywords: ksh history Message-ID: <50@gnosys.UUCP> Date: 12 Aug 88 13:58:37 GMT References: <620@gvgspd.GVG.TEK.COM> <11300001@osiris.cso.uiuc.edu> <226@ssbn.WLK.COM> <10504@ulysses.homer.nj.att.com> Reply-To: gst@gnosys.UUCP (Gary S. Trujillo) Distribution: na Organization: gst's 3B1 - Somerville, Massachusetts Lines: 21 In article <10504@ulysses.homer.nj.att.com> cjc@ulysses.homer.nj.att.com (Chris Calabrese[rs]) writes: |In article <226@ssbn.WLK.COM>, bill@ssbn.UUCP writes: |Referring to ksh history files with unique names... |> |> Not to be a nit picker, but how do you get rid of them when you log out? | |Since .profile is only read when logging in, not with every invocation - |that's what ENV is for, put something like this in your .profile: | | HISTFILE=$HOME/.kshistory$$ | /bin/ksh | rm .kshistory$$ Well, this suggestion takes care of the problem, but at the expense of an extra process per window (since there's a shell waiting around for the /bin/ksh to die). So it takes an extra slot in the process table, but maybe it doesn't matter that much since the extra shells are sharing text space, and I assume their data space is swappable. Opinions? Emmet? -- Gary S. Trujillo {ihnp4,linus,bbn,m2c}!spdcc!gnosys!gst Somerville, Massachusetts {cirl,ima,stech,wjh12}!gnosys!gst