Subject: Meaning of .pine-debug files?

From: [email-masked] (Matti Poldoja)
Date: 18 Oct 1994 10:04:37 GMT

I am new to the requirements of unix networks in providing services to other
users and have currently built pine 3.91 to run on a sunos unix platform. The
system is stand-alone, that is not connected to the rest of the world, and I
am trying to run pine without getting into the intricacies of imapd and
whatever that involves. At this point pine seems to be doing the job of
delivering the mail amongst all users, but regardless of whether mail is sent
or not, every time pine is exited by any user a .pine-debug file is created. I
know I can suppress the creation of these files by invoking pine with the -d0
option but this is not kosher with me - I prefer to get to the root of the
problem and eliminate the creation of .pine-debug files legitimately. The
problem is I cannot "see" how to correct the problem from examining the
.pine-debug file.

I have included a typical .pine-debug response (minus a few option settings
which do not seem important to the problem, in order to save space):

Debug output of the Pine program (at debug level 2).  Version 3.91
Sat Oct 15 03:53:25 1994

reading_pinerc "/usr/local/lib/pine.conf"
Read 5148 characters:
reading_pinerc "/home/root/.pinerc"
Read 5453 characters:
reading_pinerc "/usr/local/lib/pine.conf.fixed"
Open failed: No such file or directory
======= Current_val options set =======
           inbox-path : inbox
   folder-collections : mail/[]
          default-fcc : sent-mail
     postponed-folder : postponed-msgs
       mail-directory : mail
       signature-file : .signature
         address-book : .addressbook

(options deleted)...

======= Command_line_val options set =======
======= User_val options set (/home/root/.pinerc) =======
         feature-list : signature-at-bottom
 last-time-prune-ques : 94.10
    last-version-used : 3.91
======= Global_val options set (/usr/local/lib/pine.conf) =======
           inbox-path : inbox
          default-fcc : sent-mail
     postponed-folder : postponed-msgs
       mail-directory : mail

(options deleted)...

======= Fixed_val options set (NO pine.conf.fixed) =======
========== Feature settings ==========

(settings deleted)...

Userid: root
Fullname: "Operator"
User domain name being used ""
Local Domain name being used "sun2"
Host name being used "sun2"
Mail Domain name being used (by c-client too)"sun2"
Context mail/[] type: LOCAL
new win size -----<24 80>------
Terminal type: vt100
Context mail/[] type: LOCAL
About to open folder "INBOX"    inbox: "INBOX"
Opened folder "/usr/spool/mail/root" with 14 messages
Sorting by Arrival
IMAP 3:53 10/15 mm_log babble: Find of mailbox outside context: /home/root/
.pine-interrupted-mail
- mailcap_free -

    ---- MAIN_MENU_SCREEN ----

    ---- QUIT SCREEN ----
Want_to read: y (121)
expunge and close mail stream "/usr/spool/mail/root"
about to end_tty_driver
- completely_done_with_adrbks -
- mailcap_free -

Can someone please help me with what needs to be done. Thanks in advance,

Matti.
--
Matti Poldoja               | A short sig.
[email-masked]  |   is a good sig.

---

From: [email-masked] (Michael S. Scheidell)
Date: 19 Oct 1994 01:02:09 GMT

David L Miller ([email-masked]) wrote:

: The .pine-debug file is *always* created unless you suppress it with -d0.  It
: is not any indication of a problem. 

quick fix :
alias pine='/usr/local/bin/pine -d0'

--
Michael S. Scheidell                    Florida Datamation, Inc. 
[email-masked]                       (407) 241-2966
Distributers of QNX Real Time OS Products (finger for more info)

---

From: [email-masked] (David L Miller)
Date: 18 Oct 94 20:16:09 GMT

The .pine-debug file is *always* created unless you suppress it with -d0.  It
is not any indication of a problem. 

|\ |  |\/|  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 18 Oct 1994, Matti Poldoja wrote:

> Date: 18 OCT 1994 10:04:37 GMT 
> From: Matti Poldoja <[email-masked]>
> Newgroups: comp.mail.pine
> Subject: Meaning of .pine-debug files? 
>

---

From: Brad <[email-masked]>
Date: Thu, 20 Oct 1994 18:47:16 +0100

> problem is I cannot "see" how to correct the problem from examining the

	What problem? The .pine-debug files aren't created because you
have a problem; they're created every time you run Pine just because. In
case something does go wrong. Even if there isn't the teensy weensyest
little problem with your Pine session, then a .pine-debug file will be
created. They're just a precaution. So you have no need to worry. If you
don't want the .pine-debug files to be created, then like you say, you can
run pine -d0. Or this can be set in pine/osdep/os-xxx.h so that they
aren't created for any user by default. Hope this helps! 

	--Simon.

---

From: [email-masked] (David M. Williams)
Date: 19 Oct 1994 02:04:56 GMT

Matti Poldoja ([email-masked]) wrote:
: I am new to the requirements of unix networks in providing services to other
: users and have currently built pine 3.91 to run on a sunos unix platform. The
: system is stand-alone, that is not connected to the rest of the world, and I
: am trying to run pine without getting into the intricacies of imapd and
: whatever that involves. At this point pine seems to be doing the job of
: delivering the mail amongst all users, but regardless of whether mail is sent
: or not, every time pine is exited by any user a .pine-debug file is created. I
: know I can suppress the creation of these files by invoking pine with the -d0
: option but this is not kosher with me - I prefer to get to the root of the
: problem and eliminate the creation of .pine-debug files legitimately. The
: problem is I cannot "see" how to correct the problem from examining the
: .pine-debug file.

 You don't need to examine the .pine-debug file. Just go into the pine3.91/pine
directory (i.e., where the pine source code resides) and edit the makefile
appropriate to your system (e.g. makefile.sun4 for SunOS 4.1). In this file
is a line something like

DEBUG=	-g -DDEBUG

This line contains the DEBUG C pre-processor macro which turns debugging on. To
get rid of debugging and thus the .pine-debug files, you need to change this
line like so -

DEBUG=	#-g -DDEBUG

and then rebuild pine.

   .////.   .//     David M. Williams       [email-masked]
 o:::::::::///            System Manager, University of Newcastle
>::::::::::\\\	              " Amazing love! How could it be
   '\\\\\'   \\             that thou oh God shouldst die for me!"