Path: utzoo!mnetor!uunet!husc6!bbn!rochester!rutgers!mtunx!mtune!codas!ateng!chip
From: chip@ateng.UUCP (Chip Salzenberg)
Newsgroups: comp.mail.elm
Subject: Re: elm just ate my mailbox .......
Message-ID: <253@ateng.UUCP>
Date: 2 May 88 15:13:03 GMT
References: <372@m3.mfci.UUCP>
Reply-To: chip@ateng.UUCP (Chip Salzenberg)
Organization: A T Engineering, Tampa, FL
Lines: 17
Keywords: elm, munch, trashed-mailbox, I can't believe it ate the whole thing

In article <372@m3.mfci.UUCP> bronson@mfci.UUCP () writes:
>
>    Just 2 minutes ago, when I used the resyncronize command, I watched
>as elm printed out 'seek error ??? while reading mailbox' (or something
>like this) and then suddenly 60+ messages in my mailbox were gone!

We once had trouble with the resync command.  I think that our troubles
were caused by the mailbox locking, which was not appropriate for our system.
Xenix systems lock with "/tmp/basename.mlk", where 'basename' is the file
name of the mailbox in question.  For /usr/spool/mail/foo, then, the lock
file should be "/tmp/foo.mlk".

Be sure that your Elm and your mail delivery program are locking alike.
-- 
Chip Salzenberg                "chip@ateng.UU.NET" or "codas!ateng!chip"
A T Engineering                My employer may or may not agree with me.
  "I must create a system or be enslaved by another man's." -- Blake