🚀 go-pugleaf

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