Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!imp!diablery.10A.com!devil
From: devil@diablery.10A.com (Gil Tene)
Newsgroups: comp.mail.uucp
Subject: Smail 3.1 core dumping question...
Message-ID: <345@imp.UUCP>
Date: 1 Jun 91 06:35:45 GMT
Sender: devil@imp.UUCP
Organization: Diablery, cloud seven, Hell. (also 10A Inc.)
Lines: 43
Nntp-Posting-Host: imp

Hello UUCPeople,

I am running an Smail 3.1.19 configuration (straight off the
uunet archives), and I have lately been getting core dumps 
from Smail during heavy uucp mail transfers. The core dumps
are not consistent, and the data of the mail message is NOT
lost, it is sent succesfully 20 min. later during the next
smail daemon pass. I have not been able to generate these
core dumps on purpose, since it does not seem to be the 
actual mail message data that causes them, but a combination 
of data and load, probably causing some locking problems.

When smail core dumps, it sends the a mail message to the
originator of the message that failed, below is a sample 
message of this kind :


remote execution        [uucp job uunetCZbF3 (6/1-2:06:02)]
        rmail gad.fibronics!pablo
exited with status 138


        ===== stderr was =====
sh: 10123 Bus error - core dumped

The remote node (gad.fibronics) is known, and like I said 
before, this exact same execution WILL succeed if there is 
no "heavy" load of mail messages being delivered at the
same time.

Anyone out there have any ideas on how to fix this? The real
bad part is that the originator is getting a failure message
while the message is actually getting through later.

AdvThanks,

-- Gil.
-- 
--------------------------------------------------------------------
-- Gil Tene			"Some days it just dosn't pay      -
-- devil@imp.HellNet.org	   to go to sleep in the morning." -
-- devil@diablery.10A.com 					   -
--------------------------------------------------------------------