From owner-freebsd-questions  Thu Aug  6 13:40:19 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA25399
          for freebsd-questions-outgoing; Thu, 6 Aug 1998 13:40:19 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25287
          for <freebsd-questions@FreeBSD.ORG>; Thu, 6 Aug 1998 13:39:46 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id NAA28332;
          Thu, 6 Aug 1998 13:39:25 -0700 (PDT)
          (envelope-from dwhite@resnet.uoregon.edu)
Date: Thu, 6 Aug 1998 13:39:24 -0700 (PDT)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Brett Taylor <brett@peloton.physics.montana.edu>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: sendmail problem
In-Reply-To: <Pine.BSF.3.96.980804164723.249A-100000@peloton.physics.montan
 a.edu>
Message-ID: <Pine.BSF.4.00.9808061338590.28098-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Tue, 4 Aug 1998, Brett Taylor wrote:

> Hi,
> 
> Today I had sendmail die on me.  I'm running 2.2.7 and I don't THINK I'm
> doing anything weird.  I've got a couple aliases (which WERE working fine)
> defined but that's it.  I hadn't messed w/ anything, including the aliases
> for a couple of weeks.  When I look in /var/log/messages I find:
> 
> Aug  4 15:49:55 peloton /kernel: pid 26411 (sendmail), uid 0: exited on
> signal 11
> Aug  4 15:49:55 peloton sendmail[26410]: NOQUEUE: SYSERR(root): SMTP-MAIL:
> died on signal 11
> 
> I also see the same thing in maillog.  
> 
> Any ideas what's happening?  I was one of only 2 users logged in at the
> time and I was not root then either.  ftp also did not seem to be working
> for that time.

Check your memory.  If you have this problem frequently with other
programs, you may have a bad SIMM or processor cache.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message