From owner-freebsd-questions Tue Feb 5 15:58:35 2002 Delivered-To: freebsd-questions@freebsd.org Received: from isua4.iastate.edu (isua4.iastate.edu [129.186.1.204]) by hub.freebsd.org (Postfix) with ESMTP id 4350D37B41F for ; Tue, 5 Feb 2002 15:58:31 -0800 (PST) Received: from localhost (legg@localhost) by isua4.iastate.edu (8.8.8/8.8.5) with SMTP id RAA16787 for ; Tue, 5 Feb 2002 17:58:29 -0600 (CST) Date: Tue, 5 Feb 2002 17:58:29 -0600 (CST) From: Tim Legg To: freebsd-questions@freebsd.org Subject: Serious exception in FreeBSD found Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I found what I think is a serious shortcoming in FreeBSD that needs to be addressed. I am running FreeBSD 4.4-RELEASE #0: Tue Sep 18 11:57:08 PDT 2001 I executed 'tar cvf tarfile.tar ~/' while I was at my ~/ directory. The tar file was being produced when the ttyv0 was being filled with messages. Here is an example: Feb 5 17:43:56 pc047113 /kernal: microuptime() went backwards (1550895.778303 -> 1550895.-694593171) Feb 5 17:43:56 pc047113 /kernal: microuptime() went backwards (1550895.839382 -> 1550895.832517) Feb 5 17:43:56 pc047113 /kernal: microuptime() went backwards (1550895.291637 -> 1550895.274690) This made my /var/log/messages extremely huge very quickly. My /var/log/messages was growing at a rate of approximately 70,000 lines per minute. Killing the shell from another terminal didn't work since the process kept coming back with a new PID. Had to 'reboot' in order to recover If any of my users pull this off when I am not around, this could be a lot worse. Something needs to be done to fix this. Timothy D Legg legg@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message