From owner-freebsd-hackers Mon Jul 7 21:43:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27346 for hackers-outgoing; Mon, 7 Jul 1997 21:43:50 -0700 (PDT) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27324 for ; Mon, 7 Jul 1997 21:43:02 -0700 (PDT) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.8.6/8.6.9) with ESMTP id GAA17919; Tue, 8 Jul 1997 06:41:19 GMT Message-Id: <199707080641.GAA17919@peedub.gj.org> X-Mailer: exmh version 2.0delta 6/3/97 To: Julian Elischer Cc: freebsd-hackers@freefall.FreeBSD.org Subject: Re: Something screwy with 2.2.x? Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 07 Jul 1997 18:38:13 MST." <33C19A05.15FB7483@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Jul 1997 06:41:19 +0000 From: Gary Jennejohn Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer writes: >I've been seeing sporadic SIG-11 failures on busy machines >with 2.2.2+ (sources from last week. > >for example forking off 34 'ping -c 17 -s 500' >(don't ask) will cause failures in random sh and ping processes. > >It's a small machine (8MB) so there's paging going on.. >Unfortunatl;y the ping is not giving core dumps (why not?) >even wne not suid root. >the shell was doing so, but as more of the failures are happenning >in ping, I'd like to see that core-file. > >Any ideas ? > on my system ping is setuid root. Seems to me that the kernel refuses to generate core dumps for setuid processes. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com