Subject: Pine 4.21 & Solaris 7

From: Jessie Kleefstra <[email-masked]>
Date: Mon, 1 May 2000 15:23:02 -0400 (EDT)

I sent the message below, but didn't receive an answer. Does anyone have
any ideas. This is really becoming a problem.
--------

Has anyone experienced this problem and maybe have a hint as to what the
fix may be? We are running Pine 4.21 with Solaris 7. We have installed the
recommended patches. We see this happening on low to medium load.  The
error in Pine is 'formatting scroll text   80%' (the percentage is not
always the same). Pine then freezes. You could be in Pine doing anything
when the error occurs. It seems to be happening more frequently and
frequently, especially seeming to happen at a lower load. 

Our analyst has done a Truss and this is what he is seeing.
The symptoms are similar in that the functions called are the same
but the address arguments are different. The return values are the same
except for time (of course). He is attempting to rule out hardware
problems. Below is an example of the output from Truss. Any ideas?

Script started on Tue Apr 18 09:28:00 2000
mcmail# truss -p 8016
    Received signal #14, SIGALRM, in poll() [caught]
poll(0xFFBE8714, 1, 5000)			Err#91 ERESTART
time()						= 956064507
sigaction(SIGALRM, 0xFFBE7FA0, 0xFFBE80C4)	= 0
alarm(1)					= 0
setcontext(0xFFBE8370)
    Received signal #14, SIGALRM, in poll() [caught]
poll(0xFFBE8714, 1, 5000)			Err#91 ERESTART
time()						= 956064508
sigaction(SIGALRM, 0xFFBE7FA0, 0xFFBE80C4)	= 0
alarm(1)					= 0
setcontext(0xFFBE8370)
    Received signal #14, SIGALRM, in poll() [caught]
poll(0xFFBE8714, 1, 5000)			Err#91 ERESTART
time()						= 956064509
sigaction(SIGALRM, 0xFFBE7FA0, 0xFFBE80C4)	= 0
alarm(1)					= 0
setcontext(0xFFBE8370)
    Received signal #14, SIGALRM, in poll() [caught]
poll(0xFFBE8714, 1, 5000)			Err#91 ERESTART
time()						= 956064510
sigaction(SIGALRM, 0xFFBE7FA0, 0xFFBE80C4)	= 0
alarm(1)					= 0
setcontext(0xFFBE8370)
    Received signal #14, SIGALRM, in poll() [caught]
poll(0xFFBE8714, 1, 5000)			Err#91 ERESTART
time()						= 956064511
sigaction(SIGALRM, 0xFFBE7FA0, 0xFFBE80C4)	= 0
alarm(1)					= 0
setcontext(0xFFBE8370)
poll(0xFFBE8714, 1, 5000)	(sleeping...)
    Received signal #14, SIGALRM, in poll() [caught]
poll(0xFFBE8714, 1, 5000)			Err#91 ERESTART
time()						= 956064512
sigaction(SIGALRM, 0xFFBE7FA0, 0xFFBE80C4)	= 0
alarm(1)					= 0

Ad nauseum

 -----
Jessie Kleefstra                      E-Mail: [email-masked]
Sr. Consultant, Helpdesk Services     Phone: (905) 525-9140  ext.  24357        
Computing & Information Services      Fax: (905) 528-3773
ABB-132
McMaster University                 

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Robert Larmon <[email-masked]>
Date: Mon, 1 May 2000 12:38:13 -0700 (Pacific Daylight Time)

Hmm, we're running Pine 4.21 on an older system, (SunOS 4.1.4) without any
problems.  Have you installed the Maintenance Update 4, and all
Recommended and Security and Y2K patches for Solaris 7?  That usually
fixes all of my problems with Solaris 7.  Also, did you pick up the
pre-compiled binary of pine, or did you compile it yourself?

Robert

> Computing & Information Services      Fax: (905) 528-3773

```````````````````````````````````````````````````````````````````````
`			Robert Larmon				      `
`			PC Systems Analyst			      `
`			USC Law School Computing Services	      `
`			[email-masked]			      `
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

---

From: Jessie Kleefstra <[email-masked]>
Date: Tue, 2 May 2000 11:04:30 -0400 (EDT)

We are current with all of our updates. We used Sun's C compiler
(ver.4.2) to build Pine. Pine was running fine for about 2 months. The
problem seemed to start when our load went down. Any ideas?

-----

---

From: Ron Johnson <[email-masked]>
Date: Wed, 3 May 2000 18:25:54 -0700 (PDT)

> frequently, especially seeming to happen at a lower load. 
[snip]

Doing *anything*, or going to the ListFolders menu?  I had a similar
problem before, but it only occurred on the ListFolders menu, and it
didn't freeze forever.  I found out that if I got rid of the non-local
news server, and set it to:

nntp-server=

Then the problem went away.  Perhaps something similar?  Maybe try a clean
.pinerc file?

I don't know what your problem is, just typing out loud.  Hope some of it
may help. 

-- 
RJohnson.com -+- Ron Johnson <[email-masked]>
http://www2.rjohnson.com/me/2b4gyeo8EZoyG/