Subject: What is core.pine and why is it so large?

From: [email-masked] (Scott Ross)
Date: 3 May 1995 04:11:42 GMT

Hi, my provider charges extra for storage over 5MB, so I checked my disk 
space usage and core.pine was almost 3MB.  What exactly is it and why 
would it be so large?  Thanks in advance...

Scott Ross
[email-masked]

---

From: David L Miller <[email-masked]>
Date: Thu, 4 May 1995 13:55:39 -0700 (PDT)

You must have had a Pine crash at some point.  The core file is an image
of memory when the program crashed.  We would like to know the
circumstances of the crash, but the core file can be deleted... 

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

On 3 May 1995, Scott Ross wrote:

> Date: 3 May 1995 04:11:42 GMT
> From: Scott Ross <[email-masked]>
> To: [email-masked]
> Subject: What is core.pine and why is it so large?
>

---

From: Scott Ross <[email-masked]>
Date: Thu, 4 May 1995 14:10:19 -0700 (MST)

Thanks for the reply, that's a big load off of my shoulders.  I get
charged for going over 5M with my provider and that file put me
dangerously close.  The only "crash" I've ever had with Pine is when I'm
telnetting in to my provider to check my mail and my connection drops. 
That must be where the file came from.  I'm happy to report to you that I
find your program EXTREMELY stable and very easy yet powerful to use.  I
go through about 150 messages a day and have never had anything go wrong
with PINE.  I do have a problem with my carriage returns messing up
quoted text in messages (by justifying them) but am sure that is User
Error since I haven't tried to investigate it.  Again, thanks for the
reply. 

Scott Ross
[email-masked]

---

From: [email-masked] (Barry Bouwsma)
Date: 4 May 1995 23:30:58 GMT

In a previous article, [email-masked] (Scott Ross) says:

>The only "crash" I've ever had with Pine is when I'm
>That must be where the file came from.

    Perhaps...  I have an account with a service provider who is using
BSD/OS or BSD/386, and core dumps get the name of the process which was
running appended, as opposed to the simple file named core which I get
from other systems I use.  Are you, by chance, using a BSD/OS system?
    On this system, it is a frequent occurrence that people get dropped
and their orphaned Pine process spins out of control, taking as much CPU
as it can and driving the system load up.  I've told the SysAdmins here
that when they see such a Pine session, they should just kill it.  With
a signal given to a running Pine process, such as  kill -QUIT <pid>, I
can force my hung Pine sessions to create a core.pine file -- maybe your
provider has given your Pine session such a kill command...

>I do have a problem with my carriage returns messing up
>Error

    Nope, I don't think so.  I have this same problem and more when I
telnet to the BSD/OS system from NCSA telnet for the Mac -- it doesn't
appear to get the proper stty settings, so that your RETURN is sent and
interpreted as the ^J linefeed.  I can telnet to this BSD/OS from other
telnet clients and use Pine and Emacs with no problems, and I can also
telnet from Mac NCSA telnet to other OS machines and use Pine or Emacs
with no problems.  Presumably there are other telnet clients which have
problems with the BSD/OS telnetd, and other telnetd's that have problems
with Mac NCSA telnet.  I get around this by telnetting from Mac NCSA 
telnet to a different machine, from which I telnet again to the BSD/OS.
Awkward, but it works around the problems I have...

-- 
 Barry Bouwsma, will crash computers for chocolate and dental care
    Please direct mail to  <[email-masked]> (MIME-aware)
LOAD "SENDMAIL",8,1
                            driving a 300 baud Trabant on the Datenautobahn

---

From: [email-masked] (Ananda M. Kar)
Date: 23 May 1995 18:46:24 -0500

[ [email-masked] (Scott Ross) wrote the following on "comp.mail.pine": ]

-> Thanks for the reply, that's a big load off of my shoulders.  I get
-> [.......................]
-> Error since I haven't tried to investigate it.  Again, thanks for the
-> reply. 

   Put the following line in your ".cshrc" file and even if PINE crashes
   the size of core file generated will be 0.

   limit coredumpsize 0

   Remember "core" files are generated whenever a program crashes. So
   it holds for Pine, Mosaic.......and if you are an ordinary user, you
   don't need to worry about core files.

   Good Luck

   Ananda

-- 
Ananda M. Kar |(H)458-9754 | URL: http://www.cs.utexas.edu/users/ananda/
------------------------------------------------------------------------
  I am Pentium of Borg , Division is futile , You will be Approximated