From owner-freebsd-current Sat Sep 9 12:21:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA24531 for current-outgoing; Sat, 9 Sep 1995 12:21:49 -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 MAA24523 for ; Sat, 9 Sep 1995 12:21:47 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id MAA01123; Sat, 9 Sep 1995 12:20:40 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id MAA00136; Sat, 9 Sep 1995 12:22:50 -0700 Message-Id: <199509091922.MAA00136@corbin.Root.COM> To: Ollivier Robert cc: freebsd-current@freebsd.org Subject: Re: sig 11 In-reply-to: Your message of "Sat, 09 Sep 95 20:49:21 +0200." <199509091849.UAA01444@keltia.Freenix.FR> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 09 Sep 1995 12:22:49 -0700 Sender: current-owner@freebsd.org Precedence: bulk >It seems that David Greenman said: >> >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). > >I don't think it is related to this. My last major recompilation was Sep. 3 >and sed didn't show the problem when rebooting (it was at ctm#1071 dated >19950903140001). I've waited after seeing all the problem with sig 10 and >11 in -current before upgrading. > >> Let us know if you see any other programs dieing this way. Thanks. > >Not yet. I'll reboot and see if it persists. Well, this leaves me confused - are you running freebsd-stable or freebsd-current? I thought you said in your original message that you were having these problems with -stable??? -DG