[17838] in Athena Bugs
sun4 8.3.27: discuss
daemon@ATHENA.MIT.EDU (Brad Thompson)
Sat May 13 11:27:25 2000
Message-Id: <200005131527.LAA02307@manatee.mit.edu>
To: bugs@MIT.EDU
Date: Sat, 13 May 2000 11:27:19 -0400
From: Brad Thompson <yak@MIT.EDU>
System name: manatee.mit.edu
Type and version: SPARC/5 8.3.27 (with mkserv)
Display type: cgthree
Shell: /afs/sipb/project/bash/bash (/bin/athena/bash?)
Window manager: unknown
Occasionally, discuss has the following problem:
1) I type "ckm". It says that some meeting has been changed.
2) I type "nm". I then type "next" to read the new transaction.
3) I type "next". It says I have no more unread transactions.
4) I type "ckm" again. It says that the same meeting has been
changed.
I can repeat this ckm-nm-next cycle indefinitely. Inspection of the
.meetings file shows that discuss is not updating the last-read-article-number
field. This bug is reproducible. To see it for yourself, launch
discuss and add the meeting menelaus.mit.edu:/usr/spool/discuss/netusers.
Show transaction 618, then "next" to 619. Transaction 619 will not get
marked read unless you modify the .meetings file directly. I have
checked this with an empty .meetings file under the sipbtest account,
so I am convinced that it is not an account specific thing.
yak
