Path: utzoo!attcan!uunet!mmlai!burzio
From: burzio@mmlai.UUCP (Tony Burzio)
Newsgroups: comp.sys.hp
Subject: Re: .sh_history explodes...
Keywords: Curses maybe?
Message-ID: <5@gauss.mmlai.UUCP>
Date: 30 Jul 90 06:04:44 GMT
Organization: Martin Marietta Labs, Baltimore
Lines: 31

>I'm not clear on exactly what you meant by "other processes," but I
>share your suspicion that some process has the history file open, and
>hence rm doesn't really remove it, only unlinks it from the directory.

Interesting.  I didn't know that rm'ing a file could leave it behind.
Can a file exist without the inode?  Anyway, here are some more
clues:  Aborting out of curses while in cbreak mode seems to
cause the .sh_history explosion (at least, this starts the shell 
ignoring input, and the disk flashing).  In addition, exiting the session
using the pre-loaded HP-UX xctrl program (instead of the alt-ctrl-reset
of the old X) does not seem to hunt down old processes very well at
session shutdown.  Curious.

>By the way, netnews is a very slow and capricious way to get questions
>answered.  If you have either HP TeamLine or HP ResponseLine software
>support services, you can direct questions about supported HP products
>to your regional HP Response Center.  HP people who respond to netnews
>questions are donating our time.  We do not have the full resources of
>a Response Center at our disposal, and the person who knows the answer
>to any given question may not be reading news this week, or month,
>or...

In general, the Response Center has to track one of the HP Gurus down
to answer my questions.  Unfortunatly, these esteemed people are usually
busy reading the netnews :-).

*********************************************************************
Tony Burzio               * Gentlemen, this world is impaled on
Martin Marietta Labs      * a roasting spit...
mmlai!burzio@uunet.uu.net *	    - Voyage to the Bottom of the Sea
*********************************************************************