Subject: (fwd) Problems with 3.87 on a Sun

From: Jim Simmons <[email-masked]>
Date: Thu, 21 Oct 1993 08:27:20 -0400

I've seen a couple of problems with pine 3.87 on a Sun Sparc 10 (running 
SunOS 4.1.3).

First, it appears that when you save a message to another folder, the
saved message gets marked as New, even though you've already read it.  This
is not the way it worked in 3.07.  Is this normal?

Also, we've been having trouble with users who apparently loose their
connection (they're calling in through modems) and their pine process doesn't
disappear.  Sometimes it not only doesn't disappear, but apparently goes into
a loop using up as much CPU time as it can get.  Any ideas what may be
happening?

Thanks,

Jim ([email-masked])

---

From: Barry Cornelius <[email-masked]>
Date: Thu, 21 Oct 1993 14:36:57 +0100 (BST)

> a loop using up as much CPU time as it can get.  Any ideas what may be

We also have been having problems with Pine causing processes gobbling up
cpu time. This is with Pine 3.85 running on a SunOS 4.1.3 computer (called
vega).  I noticed 3 process like this a few weeks ago, one last Sunday and
3 today.  When this first occurred on 1st October, I reported it to
[email-masked]. 

I haven't managed to track down where the problem lies.  However, it seems
to occur when Pine is trying to write to the screen when the person
running Pine has logged out by some means.  It then seems to get into a
closed loop (aka infinite loop).  I have put the output from SunOS's trace
command for one of the runaway processes below.  The lines given below are
repeatedly output. 

vega# trace -p 4413
Process 4413 attached - interrupt to quit
setitimer (0, 0xefffed28, 0xefffed18) = 0
getpid () = 4413
kill (4413, 1) = - SIGHUP (1)
sigcleanup () = 0
setitimer (0, 0xefffed28, 0xefffed18) = 0
write (1, "\33[7m\33[m\7\33[22;1H\33[K", 18) = -1 EIO (I/O error)
write (1, "\33[7mA directory is selected, ent".., 95) = -1 EIO (I/O error)
sigblock (0) = 0
sigstack (0, 0xefffed2c) = 0
setitimer (0, 0xefffed28, 0xefffed18) = 0
getpid () = 4413
...

--
Barry Cornelius            Electronic mail: [email-masked]
Post:  Computing Service, University of Durham, Durham, DH1 3LE, England
Phone: Durham (091 or +44 91) 374 4717, Secretary:374 2892, Fax:374 3741

---

From: David L Miller <[email-masked]>
Date: Thu, 21 Oct 1993 09:03:41 -0700 (PDT)

Both of these are known problems.  The saved message problem will be 
fixed in an upcoming release, but it is not a trivial change.  The 
looping problem on disconnection will be fixed in the upcoming Pine 3.88 
maintenance release.  

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing
4545 15th Ave NE, Seattle WA 98105, USA

---

From: Ian Lumb <[email-masked]>
Date: Thu, 21 Oct 1993 11:59:47 -0400

We've also noticed the same problem here on a Sun 10/30 running SunOS
4.1.3. I hesitated in posting a message to this discussion group, as I
_thought_ that the problem may have been specific to our users connecting
to our Sun host via Novell ethernet. 

Ian.

--
Ian Lumb     Internet: <[email-masked]>
Earth & Atmospheric Science, York University
North York, Ontario  M3J 1P3,  CANADA
Voice: (416) 736-5245; Fax: (416) 736-5817

---

From: Mark Crispin <[email-masked]>
Date: Thu, 21 Oct 1993 12:07:38 -0700 (PDT)

> is not the way it worked in 3.07.  Is this normal?

This is a known problem, caused by a design change which permits saving of
messages to remote folders via IMAP.  Formerly, Pine had internal code to
implement saving; now it uses a generic library routine.  The problem was that
IMAP didn't have a way to support flag preservation, so in the name of
consistency flags were never preserved.  This problem has been resolved.

It is near the top of my high priority list of things to do.  Unfortunately,
it is a ``missing feature'', not a ``bug'', and so it will probably not make
it into Pine 3.88.  We have high hopes for it being in Pine 3.89 or Pine 3.90.

> a loop using up as much CPU time as it can get.  Any ideas what may be

We believe that this problem will be fixed in Pine 3.88.