home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.mail.mush
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!hirchert
- From: hirchert@ncsa.uiuc.edu (Kurt Hirchert)
- Subject: "save" overwriting rather than appending
- Message-ID: <1992Dec28.172812.22287@ncsa.uiuc.edu>
- Originator: hirchert@pluto.ncsa.uiuc.edu
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: Nat'l Ctr for Supercomp App (NCSA) @ University of Illinois
- Date: Mon, 28 Dec 1992 17:28:12 GMT
- Lines: 21
-
- Using version 7.2.1, I replied to a message and then tried to save
- that message to the same file as is specified as my outlog. (This
- was in an account used for technical support and file is intended
- to be a log of the interactions with our users, so this is a common
- operation.) First, mush put up a message about waiting to lock file
- and then it put out the normal message about appending to the file.
- However, the original message ended up in the middle of the outgoing
- message (just after the headers, overwriting the first part of the
- body of the outgoing message). Looking back at old logs, I realize
- that this has occurred before with a frequency somewhere between
- 1 in 100 and 1 in 1000.
-
- Can anyone explain why this is happening? Is there a fix to keep
- it from happening again in the future? Is there a workaround that
- will significantly reduce the likelihood of its happening?
-
- [If possible, please respond by e-mail and I will post a summary
- of responses received.]
- --
- Kurt W. Hirchert hirchert@ncsa.uiuc.edu
- National Center for Supercomputing Applications
-