tneff@bfmny0.UUCP (Tom Neff) (08/16/89)
System V/386 Release 3.2, Release 2.1. Monday, 3:23 PM. My partner is Bill Gannon... OOPS wrong show. never mind :-) Anyway, when you run mailx(1), which I'm not sure why anyone in his right mind would to begin with, the -e option (check for mail and report results via the exit code) leaves a very nice little lock file dangling after it exits (e.g., /usr/mail/tneff.lock). I found this out because I had a "mailx -e" in my profile to check for pending mail at login time, and when I installed the useful little agent "deliver" it had mild coronaries at the perennial presence of this .lock file. Deliver could be modified to actually read the lock file and verify the process number, but there's still a bug in mailx. -- "We walked on the moon -- (( Tom Neff you be polite" )) tneff@bfmny0.UU.NET
bill@twwells.com (T. William Wells) (08/17/89)
In article <14551@bfmny0.UUCP> tneff@bfmny0.UUCP (Tom Neff) writes:
: Anyway, when you run mailx(1), which I'm not sure why anyone in his
: right mind would to begin with, the -e option (check for mail and report
: results via the exit code) leaves a very nice little lock file dangling
: after it exits (e.g., /usr/mail/tneff.lock).
It's a known bug. :-( The workaround is to just check for the mailbox
yourself: if [ -s /usr/mail/tneff ];....
---
Bill { uunet | novavax | ankh | sunvice } !twwells!bill
bill@twwells.compeb@dde.uucp (Per Baekgaard) (08/17/89)
From article <14551@bfmny0.UUCP>, by tneff@bfmny0.UUCP (Tom Neff): > ... when you run mailx(1) ... with, the -e option ... [it] > leaves ... [the] lock file dangling after it exits ... Same bug exists in the interactive 386/ix system, release 2.0.0, with a mailx claiming itself to be version 3.1. -- Per Baekgaard @ GMI Data / Dansk Data Elektronik A/S, Herlev, Denmark. E-mail: peb@dde.dk or ...!uunet!mcvax!dkuug!dde!peb
kschmidt@celina.Wright.EDU (Kriss Allan Schmidt, Unix System Administrator) (08/21/89)
In article <150@caspian.dde.uucp>, peb@dde.uucp (Per Baekgaard) writes: > From article <14551@bfmny0.UUCP>, by tneff@bfmny0.UUCP (Tom Neff): > > ... when you run mailx(1) ... with, the -e option ... [it] > > leaves ... [the] lock file dangling after it exits ... > > Same bug exists in the interactive 386/ix system, release 2.0.0, with a > mailx claiming itself to be version 3.1. > It's also present in Microports Unix System V/386 Release 3.0, Version 3.0e. A what of our mailx revealed only that it was the "Final Release". BTW, we're running this on a Zenith 386. -- Lake ___ Campus : Kriss Allan Schmidt : * /| ^ | | | | | : kschmidt@celina.Wright.EDU : /__| ^ | | | `---, | | : "Learn by the Lake!" : _____|____^ V V ___| |___| :..............................:,.,\,,.,,.,,/,.