Re: exmh - presort inc sometimes fails

1999-01-07 Thread Mark Phillips

   There have been a number of reports from people recently that doing
   a presort inc sometimes fails from within exmh.  
  
  I have been doing some further experiments.  
 
 If it helps, I had it happens yesterday twice: The first time was on
 message number 140, and the second was on message number 143, IIRC.
 
 My 2 problematic messages for today, which BTW are from the same
 sender, are:
 [...messages deleted...]

Thanks for this, I have scanned the messages you included as well as
my own, looking for similarities/differences.  I think I may have discovered
a common theme.  It would seem that all the errant messages were sent using
the mailer Mutt.

My sample size it still too small to be conclusive on this point, but
it is a lead.  What could lead to an incorporation failure however is
still beyond me.

What I need to do now is get more detailed debugging info from exmh.
At the moment all the log really tells me is:

  exmh-bg {Inc_Presort +MyIncTmp: {child killed: segmentation violation}}

Does anyone know how to get more debugging info from exmh?

Thanks,

Mark.


_/\___/~~\
/~~\_/~~\__/~~\__Mark_Phillips
/~~\_/[EMAIL PROTECTED]
/~~\HE___/~~\__/~~\APTAIN_
/~~\__/~~\
__
They told me I was gullible ... and I believed them! 




nmh bug (was: Re: exmh - presort inc sometimes fails)

1999-01-07 Thread Mark Phillips

 Thanks for this, I have scanned the messages you included as well as
 my own, looking for similarities/differences.  I think I may have discovered
 a common theme.  It would seem that all the errant messages were sent using
 the mailer Mutt.
 
 My sample size it still too small to be conclusive on this point, but
 it is a lead.  What could lead to an incorporation failure however is
 still beyond me.
 
 What I need to do now is get more detailed debugging info from exmh.
 At the moment all the log really tells me is:
 
   exmh-bg {Inc_Presort +MyIncTmp: {child killed: segmentation violation}}
 
 Does anyone know how to get more debugging info from exmh?


I have just managed to reproduce the error at the commandline using
the inc command (nmh).  I have sent off a message to the nmh-workers
telling them about the bug.

Cheers,

Mark.



_/\___/~~\
/~~\_/~~\__/~~\__Mark_Phillips
/~~\_/[EMAIL PROTECTED]
/~~\HE___/~~\__/~~\APTAIN_
/~~\__/~~\
__
They told me I was gullible ... and I believed them! 




Re: nmh bug (was: Re: exmh - presort inc sometimes fails)

1999-01-07 Thread Jutta Wrage
In [EMAIL PROTECTED] Mark Phillips
[EMAIL PROTECTED] wrote:

I have just managed to reproduce the error at the commandline using
the inc command (nmh).  I have sent off a message to the nmh-workers
telling them about the bug.

It's nmh? I tried to use nmh, too, when upgrading to hamm. But then
there was no address in the to:-field, when I replied to a message.
So I changed back to mh.

cu

Jutta



exmh - presort inc sometimes fails

1999-01-04 Thread Mark Phillips
Hi,

There have been a number of reports from people recently that doing a
presort inc sometimes fails from within exmh.  The same thing has
happened to me several times.  It seems to be something to do with
certain mail files which cause the problem.  I can do a manual inc
from the command line, and this works though sometimes it pauses for a
long time before incorporating.

I have looked at the log for exmh and this is what it says:


BgAction Inc IncInner
BackgroundPending Inc
exmh-bg {Inc_Presort +MyIncTmp: {child killed: segmentation violation}}
presort inc ...
1: How do I kill the scree blank timeout in text mode?
2: Re: Communicator Installation
3: SOLVED:Re: NFS problems, cannot mount-permission denied
4: WP 8.0
5: Re: WP 8.0
6: Re: xfstt
7: How are routine tasks run , if not from cron?
8: Re: How are routine tasks run , if not from cron?
exmh-bg {FlistFindUnseen reset=0}
FlistFindStart reset=0 active=0
Flist_Done
98 unread msgs in 5 folders
exec {/usr/lib/mime/playaudio /usr/lib/exmh/drip.au}
{Sound_Feedback: /usr/lib/mime/playaudio: /dev/audio: Permission denied}
exec {/usr/lib/mime/playaudio /usr/lib/exmh/drip.au}
{Sound_Feedback: /usr/lib/mime/playaudio: /dev/audio: Permission denied}
exmh-bg {Flist_FindUnseen end {196752 microseconds per iteration}}
BackgroundComplete Inc
background actions complete


So it seems to bomb out with a sementation violation, so that it doesn't
incorporate beyond the 8th message.  Maybe there's something wrong with
the 9th email?


Cheers,

Mark.


_/\___/~~\
/~~\_/~~\__/~~\__Mark_Phillips
/~~\_/[EMAIL PROTECTED]
/~~\HE___/~~\__/~~\APTAIN_
/~~\__/~~\
__
They told me I was gullible ... and I believed them! 




Re: exmh - presort inc sometimes fails

1999-01-04 Thread Mark Phillips
 There have been a number of reports from people recently that doing
 a presort inc sometimes fails from within exmh.  

I have been doing some further experiments.  

The output from exmh is as follows:


BgAction Inc IncInner
BackgroundPending Inc
exmh-bg {Inc_Presort +MyIncTmp: {child killed: segmentation violation}}
presort inc ...
1: How do I kill the scree blank timeout in text mode?
2: Re: Communicator Installation
3: SOLVED:Re: NFS problems, cannot mount-permission denied
4: WP 8.0
5: Re: WP 8.0
6: Re: xfstt
7: How are routine tasks run , if not from cron?
8: Re: How are routine tasks run , if not from cron?
exmh-bg {FlistFindUnseen reset=0}

etc etc...

It only does the first 8 messages.  So the problem occurs, it would
seem, at the 9th message.  I edited the mail file, removing messages from
the tail of the file.  Sure enough, it was when I removed the 9th message
that the problem stopped.  However there is a twist.  When I left the 9th
message there and removed the first message, the problem stopped.

So it seems the problem is not with the 9th message per se, but rather,
with the complete set of the first 9 messages.

I enclose the 9 messages which cause the problem, here:


###-
From debian-user@lists.debian.org Sat Dec 26 08:18:09 1998
Return-path: debian-user@lists.debian.org
Envelope-to: [EMAIL PROTECTED]
Delivery-date: Sat, 26 Dec 1998 08:18:09 +1030
Received: from localhost [127.0.0.1] (root)
by localhost with esmtp (Exim 1.92 #1 (Debian))
id 0ztf5c-Gp-00; Sat, 26 Dec 1998 08:18:08 +1030
Received: from adam.ist.flinders.edu.au
by localhost (fetchmail-4.3.9 POP3)
for mark/localhost (single-drop); Sat, 26 Dec 1998 08:18:08 CST
Received: from murphy.novare.net (murphy.debian.org [209.176.56.6])
by adam.ist.flinders.edu.au (8.8.5/8.8.5) with SMTP id BAA20991
for [EMAIL PROTECTED]; Sat, 26 Dec 1998 01:31:22 +1030 (CST)
Received: (qmail 31800 invoked by uid 38); 25 Dec 1998 15:00:48 -
Resent-Date: 25 Dec 1998 15:00:48 -
Resent-Cc: recipient list not shown: ;
X-Envelope-Sender: [EMAIL PROTECTED]
Subject: How do I kill the scree blank timeout in text mode?
To: debian-user@lists.debian.org (Debian User List)
Date: Fri, 25 Dec 1998 10:00:42 -0500 (EST)
From: Stan Brown [EMAIL PROTECTED]
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID: Fn-YgD.A.hwH.fi6g2@murphy
Resent-Message-ID: Fn-YgD.B.hwH.fi6g2@murphy
Resent-From: debian-user@lists.debian.org
X-Mailing-List: debian-user@lists.debian.org archive/latest/30642
X-Loop: debian-user@lists.debian.org
Precedence: list
Resent-Sender: [EMAIL PROTECTED]
X-UIDL: 027e5c386efa4f6af8e90f58567f43f1

I just installed 2.0, and I am anoyed by my screen blanking out. How do
I change this configuration to not blank?

-- 
Stan Brown [EMAIL PROTECTED]770-996-6955
Factory Automation Systems
Atlanta Ga.
-- 
Windows 98: n.
minor patch release for 32-bit extensions and a graphical shell for a
16-bit patch to an 8-bit operating system originally coded for a 4-bit
microprocessor, written by a 2-bit company that can't stand for 1 bit
of competition.
-
(c) 1998 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


-- 
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  
/dev/null



From debian-user@lists.debian.org Sat Dec 26 08:18:10 1998
Return-path: debian-user@lists.debian.org
Envelope-to: [EMAIL PROTECTED]
Delivery-date: Sat, 26 Dec 1998 08:18:10 +1030
Received: from localhost [127.0.0.1] (root)
by localhost with esmtp (Exim 1.92 #1 (Debian))
id 0ztf5d-Gp-00; Sat, 26 Dec 1998 08:18:09 +1030
Received: from adam.ist.flinders.edu.au
by localhost (fetchmail-4.3.9 POP3)
for mark/localhost (single-drop); Sat, 26 Dec 1998 08:18:09 CST
Received: from murphy.novare.net (murphy.debian.org [209.176.56.6])
by adam.ist.flinders.edu.au (8.8.5/8.8.5) with SMTP id BAA21093
for [EMAIL PROTECTED]; Sat, 26 Dec 1998 01:53:49 +1030 (CST)
Received: (qmail 3676 invoked by uid 38); 25 Dec 1998 15:23:05 -
Resent-Date: 25 Dec 1998 15:23:05 -
Resent-Cc: recipient list not shown: ;
X-Envelope-Sender: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
X-Originating-IP: [209.178.83.166]
From: KTB . [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Subject: Re: Communicator Installation
Date: Fri, 25 Dec 1998 07:22:32 PST
Mime-Version: 1.0
Content-Type: text/plain
Resent-Message-ID: PxYboD.A.N5.Y36g2@murphy
Resent-From: debian-user@lists.debian.org
X-Mailing-List: debian-user@lists.debian.org archive/latest/30643
X-Loop: debian-user@lists.debian.org
Precedence: list
Resent-Sender: [EMAIL PROTECTED]
X-UIDL: 0966a614f7169d8c710471827d3f37cb

Date: Fri, 25 Dec 1998 00:21:40 -0600 (CST)
From: Kent West [EMAIL PROTECTED]
To: KTB [EMAIL