From owner-freebsd-current  Sat Sep  9 10:27:45 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id KAA20661
          for current-outgoing; Sat, 9 Sep 1995 10:27:45 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA20652
          for <freebsd-current@freebsd.org>; Sat, 9 Sep 1995 10:27:43 -0700
Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id KAA00867; Sat, 9 Sep 1995 10:26:33 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id KAA04524; Sat, 9 Sep 1995 10:28:42 -0700
Message-Id: <199509091728.KAA04524@corbin.Root.COM>
To: Ollivier Robert <roberto@keltia.freenix.fr>
cc: freebsd-current@freebsd.org (FreeBSD Current Users' list)
Subject: Re: sig 11 
In-reply-to: Your message of "Sat, 09 Sep 95 18:59:18 +0200."
             <199509091659.SAA00258@keltia.Freenix.FR> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sat, 09 Sep 1995 10:28:30 -0700
Sender: current-owner@freebsd.org
Precedence: bulk

>Is the problem with sig 11 supposed fixed ? 
>
>I just upgraded to CTM cvs-cur #1083,
>
>CTM_BEGIN 2.0 cvs-cur 1083 19950909080002Z .
>
>rebuilt  a kernel and the lkms  and I begin to  get sig11 on sed at startup
>(by the news user). They are the only so far but it is disturbing...
...
>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.

-DG