Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!fletcher
From: fletcher@cs.utexas.edu (Fletcher Mattox)
Newsgroups: comp.mail.mush
Subject: mush signals
Message-ID: <5505@cs.utexas.edu>
Date: 11 May 89 03:49:55 GMT
Organization: U. Texas CS Dept., Austin, Texas
Lines: 19

If you use DOT_LOCK, mush doesn't ignore signals in copyback() until
*after* the folder has been truncated.  This can be Bad News if a
signal is received while trying to write back your spool mailbox.
Especially if disk io is a little sluggish, say because of an NFS retry
or two ...

And even after you have turned on IGN_SIGS, doesn't this code in
catch() defeat it?

    if (ison(glob_flags, IGN_SIGS) && sig != SIGTERM && sig != SIGHUP)
	    return;

which suggests that HUP and/or TERM will not be ignored while writing
your folder.

The reason I ask is that we have seen a couple instances of corrupted
spool mail files with DOT_LOCK and HOMEMAIL defined in an NFS environment.

Fletcher