🚀 go-pugleaf

I've just upgraded the machine I use to read mail to A/UX 2.0 and I'm now 
having problems with mush (Mail User's Shell) version 6.5.  Everything works
fine until I try to quit mush and then the process hangs.  I assume that it
must be hung inside the kernel somewhere, because I can't kill it even using
'kill -9' as root, and even shutting the machine down to single-user mode
doesn't kill it.  As a result, if I reboot the machine to get rid of the
process, one of the file systems can't be unmounted and A/UX has to re-check
it.

As long as the process is hung, I also get 'portmapper not responding; giving
up' messages about every ten seconds on the console.  The port mapper *is*
running, and everything else I've thought to check is fine as well.  This
program worked fine under 1.1 and I did try recompiling it, but nothing has
helped.

I've also checked the permissions on the mail file and they're ok.  Even
with a mush process hung and 'fuser /usr/mail/davism' showing that the mush
process is using the mail file, mailx has no problems accessing or updating
the mail file.

I tried mush (7.1) on a different machine and got nothing but two error messages
that said "No record locks available".  I checked, and I had disabled rpc.lockd
(for some problem that I don't remember).  So I restarted rpc.lockd and tried
again.  This time I got the same hangup that I had on the original machine, 
PLUS the Mac environment crashed into MacsBug and I finally just had to reset
the machine.

So has anyone else run into any problems related to record locking?  Or do I
have mush configured incorrectly?

If anyone can offer suggestions or help (via e-mail) I'll appreciate it.

-------------------------------------------------------------------------------
                      Mat Davis (davism@vtopus.cs.vt.edu)
                 Department of Computer Science, Virginia Tech
-------------------------------------------------------------------------------