🚀 go-pugleaf

Since I'm looking for a good X based mailer to use in conjunction with elm
(for those days that you just *want* to point and click), I decided to try
the OpenWindows 3.0 Mailtool.  

Anyway, here's the problem:  while in the mailtool I sent a message to
myself.  Filter barfed with the following:

filter (weisen): Couldn't create lockfile ******
filter (weisen): Can't open mailbox /usr/spool/mail/weisen!
filter (weisen): Using /afs/alw.nih.gov/dcrt/weisen/EMERGENCY_MBOX as
emergency mailbox

where the ****** is a bunch of international characters.  Now the fact that
it didn't report the name of the lockfile seems to be a bug in the filter
code in actions.c (it uses this array called lockfile but doesn't seem to
place anything in it -- lock() uses a different pointer called lockfile;
maybe I missed something there).

Disregarding the fact that the error message is hosed, does anyone know what
the locking conflict between the OW Mailtool and Elm is?


Thanks,
Neil


here's some diagnostic bugaboo:

/afs/alw.nih.gov/dcrt/weisen/.sun4/bin/filter:
	$Id: actions.c,v 5.3 1992/12/24 19:22:05 syd Exp $
	$Id: buffer.c,v 5.1 1992/10/03 22:18:09 syd Exp $
	$Id: filter.c,v 5.3 1992/11/15 01:40:43 syd Exp $
	$Id: lock.c,v 5.5 1992/12/07 03:49:49 syd Exp $
	$Id: parse.c,v 5.6 1992/12/11 01:45:04 syd Exp $
	$Id: rules.c,v 5.5 1992/12/11 01:45:04 syd Exp $
	$Id: summarize.c,v 5.6 1992/12/11 01:45:04 syd Exp $
	$Id: utils.c,v 5.2 1992/11/15 01:40:43 syd Exp $
	$Id: mk_lockname.c,v 5.1 1992/10/03 22:41:36 syd Exp $
	$Id: istrcmp.c,v 5.1 1992/10/03 22:41:36 syd Exp $

and from elm -v:

	Following mail spool locking protocols will be used:
	USE_DOTLOCK_LOCKING (.lock) USE_FLOCK_LOCKING USE_FCNTL_LOCKING


--
Neil I. Weisenfeld                    National Institutes of Health
Computer Engineer                     Building 12A, Room 2033
weisen@alw.nih.gov                    Bethesda, MD 20892
uunet!nih-csl!weisen                  phone: (301) 402-2788