Subject: problem on SCO Unix on 486

From: [email-masked] (Jon Zeeff)
Date: 17 Jul 1995 12:16:58 -0400

We continue to have a problems when using the Pine software for various 
users. They keep receiving the following message:

       Bug in Pine detected "rec'd abort signal"
       exiting Pine
       attempting to save debug file to /usr/garnet/pine crash

We then hit any key to continue.
When we try to use Pine for this user again it cannot open their INBOX.
It locks them up in our computer and we then have to kill the process 
using the root directory command.
Any solutions on how to correct this problem?

Any ideas on this?  Does anyone have a SCO Unix binary that I could get
a copy of?

-- 
        Commercial Internet Marketing and WWW Development
Jon Zeeff       Branch Information Services     [email-masked]
(313) 741-4442  http://branch.com/              gopher branch.com

---

From: [email-masked] (Gunther Anderson)
Date: 19 Jul 1995 14:08:37 GMT

Jon Zeeff ([email-masked]) wrote:
: We continue to have a problems when using the Pine software for various 
: users. They keep receiving the following message:

:        Bug in Pine detected "rec'd abort signal"
:        exiting Pine
:        attempting to save debug file to /usr/garnet/pine crash

No idea.  Is the pine.crash file telling you anything especially 
interesting?  You might also build with -g, and go do a stack trace on 
the core file.  Also, are you using sendmail or MMDF?

: We then hit any key to continue.
: When we try to use Pine for this user again it cannot open their INBOX.
: It locks them up in our computer and we then have to kill the process 
: using the root directory command.
: Any solutions on how to correct this problem?

This second part is actually a file locking problem, most likely.  The
previous instance did not have a chance to remove the locking file for the
mailbox, and the new instance detects the lock file, but can't find a
process to alert that it's taking it.  Pine's solution is to wait
patiently for five minutes for the process to respond, and then remove the
lock file and go on with its life.  The lock file is
/usr/spool/mail/username.lock, which you can remove yourself.  Or just
wait for five minutes until it gives up. 

: Any ideas on this?  Does anyone have a SCO Unix binary that I could get
: a copy of?

Try the compiled binaries available on ftp.celestial.com (there are two 
sets), and odi.cwc.whecn.edu (just one set).