[2847] in Athena Bugs
xmh confusion
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Sun Aug 13 19:34:49 1989
Date: Sun, 13 Aug 89 19:34:33 -0400
From: Ken Raeburn <raeburn@ATHENA.MIT.EDU>
To: bugs@ATHENA.MIT.EDU
RT 6.3B...
(Have I already complained about xmh assuming it can create/write
.xmhcache? That prevents it from being usable to read other mh
directories that aren't writable. John's got one that is
world-readable that I'd like to peruse, but I can't with xmh....)
If a message is not writable, xmh will not display it. For some
reason, the call
open (filename, O_RDONLY | O_CREAT, 0666)
fails and returns -1. I don't know why; the file is readable to me.
(Why is xmh opening a supposedly existing message with O_CREAT?
Silently creating it is not the right way to fix lossage...) My
homedir is in AFS, but .mh/gcc is a link to /mit/jfc/Mail/gcc, which
is NFS. Turning off the O_CREAT flag does fix the problem. This
might be a problem in our kernels.
It appears that xmh (in the EDiskSrc widget) fails to check the return
value of the `open' call, tries `fstat' on the -1 result, and uses
unassigned results to determine the size of space to be allocated.
Thus, it dies with a completely bogus "cannot malloc" message....
The error message window popped up when re-scanning a folder generates
an error message (such as "no messages in ...") has editable text, and
the "X" cursor in the "acknowledge" button.
-- Ken
