From owner-freebsd-current  Thu Oct 15 10:04:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA22490
          for freebsd-current-outgoing; Thu, 15 Oct 1998 10:04:32 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from plethora.techv.net ([205.210.170.77])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22485
          for <freebsd-current@FreeBSD.ORG>; Thu, 15 Oct 1998 10:04:28 -0700 (PDT)
          (envelope-from darin@slovitt.net)
Received: from localhost (darin@localhost)
	by plethora.techv.net (8.8.8/8.8.8) with ESMTP id NAA05938;
	Thu, 15 Oct 1998 13:04:10 -0400 (EDT)
Date: Thu, 15 Oct 1998 13:04:09 -0400 (EDT)
From: Darin Slovitt <darin@slovitt.net>
X-Sender: darin@plethora.techv.net
To: Doug White <dwhite@resnet.uoregon.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Limits Problems ...
In-Reply-To: <Pine.BSF.4.03.9810150926570.12131-100000@resnet.uoregon.edu>
Message-ID: <Pine.BSF.4.03.9810151300490.5150-100000@plethora.techv.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 15 Oct 1998, Doug White wrote:

> This sounds like the timewarping clock bug that's been popping up on
> systems running APM.  If you're using the APM driver try knocking it out
> of your kernel.

Unfortunatly I don't have APM in my kernel. It was one of the first things
that I took out.

> Don't forget, when you modfiy /etc/login.conf, run cap_mkdb afterwards.

Always.

Thanks for the suggestion, anything else that you can think of?

--
TTYS :-)
Darin Slovitt


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