[6971] in Athena Bugs
vax 7.2P: help -ttymode "Release-->Full"
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Mon Jan 28 11:59:12 1991
Date: Mon, 28 Jan 91 11:58:52 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: ckclark@ATHENA.MIT.EDU
Cc: bugs@ATHENA.MIT.EDU
In-Reply-To: bugs[6945]
I cannot duplicate the problem you describe; when I try to view the
document in question on a 7.2P CVAXSTAR workstation with help -tty, it
works just fine, and very quickly.
Did you have the andrew locker attached when you did this? Is it
still reproduceable for you?
Jonathan Kamens
Project Athena Quality Assurance
Reference:
Date: Thu, 24 Jan 91 06:34:27 EST
From: The Hammer <ckclark@ATHENA.MIT.EDU>
System name: test-3100
Type and version: CVAXSTAR 7.2P
Display type: SM
What were you trying to do?
Use 'help -ttymode' go look at Release Notes for 7.2:
6* Athena 7.2 Release (January 1991) [DRAFT ONLY]
Most of the stuff in this section works okay, although
formatted poorly, but when I tried to select
7 Full Document
the program hung for a while, and I discovered that it
was writing an enormous file in /usr/tmp:
/usr/tmp% df /site
Filesystem kbytes used avail capacity Mounted on
/dev/rz3g 49982 45004 0 100% /site
/usr/tmp% ls -l foo.1872
-rw-rw-r-- 1 ckclark 12976128 Jan 24 05:34 foo.1872
/usr/tmp% file foo.1872
foo.1872: English text
/usr/tmp%
I tried to "more" the file foo.1872, and in seems to
have text about Andrew and stuff in it. It looked
like it might be an EZ type data file (it contained
non-ascii characters), but I am not sure. Anyway,
it is repeatable, so you can try it. Oh, and 1872
is not the PID of the help, it is the PID of
a 'sh' it spools off. (In case that helps.)
What's wrong:
Oh, nothing much, really. But a naive user might
go into a conniption if /site fills and he/she can't
figure out what to do. Someone asked me about
the new release, and I almost told him to look
there instead of doing it myself first to check.
What should have happened:
If it's not ready, it should give a message saying
'Not available' or something. It definitely should
not dump a dozen-meg file into /usr/tmp with the
wonderfully informative name 'foo.####'.
Please describe any relevant documentation references:
N/A. I'll take a look at the release description
on the 'info' locker instead.
