[5651] in Athena Bugs
vax 7.0F: xmh and AFS
daemon@ATHENA.MIT.EDU (Anne R. LaVin)
Wed Aug 1 12:04:30 1990
To: bugs@ATHENA.MIT.EDU
Date: Wed, 01 Aug 90 12:04:13 EDT
From: Anne R. LaVin <lavin@ATHENA.MIT.EDU>
System name: laika
Type and version: CVAXSTAR 7.0F
Display type: SM
What were you trying to do?
use xmh to reply to a message
What's wrong:
Here's what happened:
I tried to reply to a mail message in xmh, and it beeped, disappeared,
and the following message appeared in my console:
11:51 xmh: Permission denied
11:51 xmh: Error in FOpenAndCheck(/mit/lavin/Mail/drafts/.xmhcache, r)
11:51 errno = 13; Permission denied
11:51 exiting.
So, I went to an xterm and typed:
xmh -geometry 495x675-2+2&
And it replied:
[1] 137
laika% xmh: Can't create or read mail directory!
errno = 13; Permission denied
exiting.
[1] Exit -1 xmh -geometry 495x675-2+2
So, I checked that I was in my homedir, and could, indeed list the
files in my homedir. I could both list and create files in
/mit/lavin, but when I tried to list files in /mit/lavin/Mail, I got:
laika% ls Mail
Mail unreadable
So, I checked my tokens:
Tokens held by the Cache Manager:
[ 1]Tokens for afs@athena.mit.edu [Expires Aug 1 17:07]
[ 2] --End of list--
and my tickets:
Ticket file: /tmp/tkt_ttyv0
Principal: lavin@ATHENA.MIT.EDU
Issued Expires Principal
Aug 1 09:07:38 Aug 1 17:07:38 krbtgt.ATHENA.MIT.EDU@ATHENA.MIT.EDU
Aug 1 09:07:46 Aug 1 17:07:46 afs.athena.mit.edu@ATHENA.MIT.EDU
Aug 1 09:07:58 Aug 1 17:07:58 rvdsrv.odysseus@ATHENA.MIT.EDU
Aug 1 09:08:03 Aug 1 17:08:03 rvdsrv.talos@ATHENA.MIT.EDU
Aug 1 09:08:22 Aug 1 17:08:22 zephyr.zephyr@ATHENA.MIT.EDU
Aug 1 09:08:29 Aug 1 17:08:29 pop.e40-po@ATHENA.MIT.EDU
Aug 1 09:08:44 Aug 1 17:08:44 olc.matisse@ATHENA.MIT.EDU
And they were all fine. I called Ezra in (he had the misfortune to be
walking by at the time), and he suggested that doing a
fs flush Mail
might fix it, and it did.
I have absolutely no idea what actually happened, but he suggested
that I might want to send a bug report on it, so here it is. Hope
it's complete enough.
What should have happened:
well, it should have just let me reply to the message! :)
Please describe any relevant documentation references:
[Please replace this line with your information.]
