Subject: Re: pine process

From: Matt Simmons <[email-masked]>
Date: Mon, 8 Nov 1993 15:10:29 -0600 (CST)

To the list people:  This pine will process was mailing a user named 
will, and had been suspended.  Why would it still be sucking up CPU 
cycles while suspended.  If it matters, I had logged out without killing 
the job.

On Mon, 8 Nov 1993, Pete Hartman wrote:
> You need to be more careful.  I just killed a process running "pine 
> will" that had racked up over *52000* CPU minutes.  Don't let it 
> happen again.

Devoted    _n______________________________________________  _________________
Teri      /   \|[]|""  \    |[]|   |[]|   |[]|   |[]|    / || \    |[]|   |[]|
Polo    ,(_____|  |()_()\___|  |___|  |___|  |___|  |___/  ||  \___|  |___|  |
Fan    <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__|
=========\   Walt Disney World Monorail System             ||
LCA  _____\________________________________________________||_________________
  __/ This highway's in perfect shape.  Quick!         Thank god I'm not a
_/ Break it so we can 'fix' it! -- IDOT Motto              F. I. P. =)

---

From: David L Miller <[email-masked]>
Date: Mon, 8 Nov 1993 13:28:50 -0800 (PST)

Pine 3.87 has an annoying little bug that crops up when you get 
disconnected while in the composer.  Basically, it is waiting for 
user input, detects an I/O failure, and tries to kill itself.  
Unfortunately, the signal handler just sets a flag and returns to the 
input loop :(

This will be fixed in Pine 3.88 which should be out later this week.

|\ |  |\/|  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