From owner-freebsd-current  Sat Sep  9 11:51:50 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id LAA23521
          for current-outgoing; Sat, 9 Sep 1995 11:51:50 -0700
Received: from irbs.irbs.com (irbs.com [199.182.75.129])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA23515
          for <freebsd-current@freebsd.org>; Sat, 9 Sep 1995 11:51:46 -0700
Received: (from jc@localhost) by irbs.irbs.com (8.6.12/8.6.6) id OAA16895; Sat, 9 Sep 1995 14:51:24 -0400
From: John Capo <jc@irbs.com>
Message-Id: <199509091851.OAA16895@irbs.irbs.com>
Subject: Re: sig 11
To: archive@cps.cmich.edu (Mail Archive)
Date: Sat, 9 Sep 1995 14:51:22 -0400 (EDT)
Cc: davidg@Root.COM, roberto@keltia.freenix.fr, freebsd-current@freebsd.org
In-Reply-To: <Pine.SUN.3.91.950909143240.20036A-100000@cps201> from "Mail Archive" at Sep 9, 95 02:35:11 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1095      
Sender: current-owner@freebsd.org
Precedence: bulk

Mail Archive writes:
> 
> On Sat, 9 Sep 1995, David Greenman wrote:
> 
> > ...
> > >pid 123: sed: uid 8: exited on signal 11
> > >pid 126: sed: uid 8: exited on signal 11
> > 
> >    I brought in the sed SCO compatibilty changes from -current, and this may
> > be related. If this is the case, I will back out the changes (I don't have any
> > time to troubleshoot the problem).
> >    Let us know if you see any other programs dieing this way. Thanks.
> > 
> With sup'ed to -current on two machines (Tuesday sept5 was the sup date) 
> and after make worlds on both of them we get the Exact same problem with 
> Sig 11. Since the start of Sig 11's my boss wants us to move back to 
> Debian Linux. I would perfer just to resup and recompile and get this 
> fixed and not have to restart the machines from scratch.
> 

These kinds of problems are all part of running -current.  Current
is a development tree and is quite often broken for one reason or
another.  Like the docs say, "The bleeding edge".

Sounds like you should be running -stable rather than -current.

John Capo
IRBS Engineering