From owner-freebsd-current Mon Dec 22 09:30:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA08348 for current-outgoing; Mon, 22 Dec 1997 09:30:34 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08320 for ; Mon, 22 Dec 1997 09:30:19 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id JAA01170; Mon, 22 Dec 1997 09:29:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712221729.JAA01170@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: John Polstra cc: current@freebsd.org Subject: Re: Random core dumps In-reply-to: Your message of "Mon, 22 Dec 1997 09:17:29 PST." <199712221717.JAA18413@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Dec 1997 09:29:43 -0800 From: Amancio Hasty Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The other thing to consider is doing a power cycle to reset the box. Sometimes win95 leaves the machine in a weird state whose symptom is that some processes start core dumping like netscape. With respect to ld.so , some of applications after the ld.so change started core dumping at random intervals and the only change that I did to the system was to replaced ld.so that appears somehow to cure the problem . So far the system is behaving very well with a system sup as of Sunday. Amancio