From owner-freebsd-stable  Tue Feb  9 16:12:34 1999
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA03982
          for freebsd-stable-outgoing; Tue, 9 Feb 1999 16:12:34 -0800 (PST)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from quicksand.desert.kconline.com (quicksand.desert.kconline.com [208.154.67.253])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03975
          for <freebsd-stable@FreeBSD.ORG>; Tue, 9 Feb 1999 16:12:31 -0800 (PST)
          (envelope-from rif@kconline.com)
Received: from localhost (rif@localhost)
	by quicksand.desert.kconline.com (8.9.2/8.9.1) with ESMTP id TAA02971;
	Tue, 9 Feb 1999 19:11:58 -0500 (EST)
	(envelope-from rif@kconline.com)
Date: Tue, 9 Feb 1999 19:11:58 -0500 (EST)
From: Jim Riffle <rif@kconline.com>
X-Sender: rif@quicksand.desert.kconline.com
To: Blaz Zupan <blaz@gold.amis.net>
cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Spontaneous reboots
In-Reply-To: <Pine.BSF.4.05.9902091903470.2929-100000@quicksand.desert.kconline.com>
Message-ID: <Pine.BSF.4.05.9902091905170.2943-100000@quicksand.desert.kconline.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> Also if you have a good idea how we could attack the problem, please speak
> up. For now my idea is to find a common software and hardware
> configuration and then try to sistematically remove components that could
> cause the problem.

A while back I ran into this problem and found that I was running into
resource limits on open files, processes, etc.  It may be worth while
checking your settings in /etc/login.conf and keeping an eye on 'pstat -T'
output.

Jim


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message