[2411] in SIPB bug reports
edsc
daemon@ATHENA.MIT.EDU ("Mark W. Eichin")
Tue Jan 28 22:47:24 1992
Date: Tue, 28 Jan 92 22:46:39 -0500
From: eichin@ATHENA.MIT.EDU ("Mark W. Eichin")
To: tytso@athena.mit.edu
Cc: warlord@MIT.EDU, bug-sipb@MIT.EDU
In-Reply-To: Theodore Ts'o's message of Tue, 28 Jan 92 22:33:45 -0500 <9201290333.AA24360@tsx-11.MIT.EDU>
SUB: Re: edsc
SUM: tytso (Theodore Ts'o), tytso->Derek Atkins <warlord>, bug-sipb
Date: Tue, 28 Jan 92 14:17:17 EST
From: Derek Atkins <warlord@MIT.EDU>
I was over quota at the time, so no writing-out was happening.
However, discuss did not give me an error. It just kept on
going as if everything were working fine. The only indication that
something was wrong was after I finished catching up on ALL my meetings
(except one), I did a list, and all those meetings came up again!
edsc should report writing errors to the user!
It does. When you exited the meeting, it should have beeped, and
displayed the message "Disk Quota Exceeded" on the minibuffer line.
I suspect you didn't notice it. Perhaps in order to report that error,
edsc should replace the *meetings* buffer with an *error* buffer that
contains "You're over quota" repeated several hundred times. :-)
It was on a VS/2, slow enough for this to be visible. It did *NOT*
beep, it did *not* display any message on the minibuffer line. (Note
also that doing "c" for catchup also caused no messages to appear, and
no beeping either.) [I was trying to figure this out too...] This was
with an NFS filesystem, not AFS.
_Mark_
