[8253] in Athena Bugs

home help back first fref pref prev next nref lref last post

No subject found in mail header

daemon@ATHENA.MIT.EDU (honor@Athena.mit.edu)
Sun Sep 22 15:14:20 1991

From: honor@Athena.mit.edu
To: bugs@Athena.mit.edu, bug@Athena.mit.edu
Cc: honor@Athena.mit.edu
Date: Sun, 22 Sep 91 15:14:55 EDT


Not even sure if these are the right mailing lists, but...

A few days ago I logged in and my fileserver was down.  I got a temp
directory and a warning that any mail I inc'ed would be lost.  I had
heard that with the new release this wasn't so, so decided to check.  I
inc'ed the mail.  Then I used "from -v" to see if it was still at the
PO, which it was.  And indeed, the temp .mh_profile had specified the
notruncate option to inc.

Not too long after that I attempted to login on a few different
workstations, but since my fileserver was down, I couldn't.  After
trying to login, it said it couldn't attach my homedir, and asked if I'd
like to try again (to which I answered yes).  After the second attempt
to attach my homedir failed, it just aborted the login process, instead
of asking if I wanted to continue with a temp directory.

Not too long after that, I attempted to login on 'test-3100', and my
fileserver was down (If you haven't guessed already, it's aphrodite).
This time I was allowed to login with a temp directory though.  However,
I incorporated mail, and lost it.  I assumed (yeah, big mistake), that
inc would be using the notruncate option, but evidently it didn't.

Luckily none of the mail I lost was that important, but I'd still
suggest a bit more consistency...  Users should have a chance to login
with a temp dir, the notruncate option to inc should be used by default
when they do login with a temp dir, and because of this, they shouldn't
receive the warning about inc'ing mail when they do login.

Thanx for listening, and please let me know if I sent this to the wrong
mailing lists.


Andy Cassidy
honor@athena

home help back first fref pref prev next nref lref last post