From owner-freebsd-current  Thu Sep 21 23:10:43 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id XAA16471
          for current-outgoing; Thu, 21 Sep 1995 23:10:43 -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 XAA16466
          for <current@freebsd.org>; Thu, 21 Sep 1995 23:10:41 -0700
Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id XAA01284; Thu, 21 Sep 1995 23:09:23 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id XAA00445; Thu, 21 Sep 1995 23:11:50 -0700
Message-Id: <199509220611.XAA00445@corbin.Root.COM>
To: asami@cs.berkeley.edu (Satoshi Asami)
cc: current@freebsd.org
Subject: Re: sig 10/11 problems 
In-reply-to: Your message of "Thu, 21 Sep 95 22:14:26 PDT."
             <199509220514.WAA00765@silvia.HIP.Berkeley.EDU> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Thu, 21 Sep 1995 23:11:49 -0700
Sender: owner-current@freebsd.org
Precedence: bulk

> *    Is the problem you're having with specific binaries, and does it always
> * fail? I think you might have a corrupt binary and/or shared library. Except
> * for a shell bug reported by Stephen Hocking, all of the reports I've gotten
> * back have indicated that the patch has gotten rid off all of the sig 10/11
> * flakiness they were experiancing.
>
>They are all X programs, like xterm, xload, etc.  When I start X, the
>screen goes gray (so the server is fine), waits there for a while and
>then comes back to the console with a whole bunch of messages and a
>bunch of *.core files.
>
>This is exactly what I was seeing before.  Other programs (sed and
>stuff) have never failed for me.

   Sorry everyone...I changed the wrong 'doclusterread' in the file on
freefall before I committed it. Thanks to Poul-Henning for telling me that
the patch I sent him (which worked) and what I actually committed (bogus)
were different! ...and thanks to Steven Wallace for trying to point out the
mistake originally (you should be more assertive Steven! :-)).
   Okay, the _correct_ change is now committed (changing both cases of
doclusterread just to be certain!)...this should be available from SUP in
at about 3AM PDT.

-DG