From owner-freebsd-bugs Tue Feb 5 16:27:16 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id D8B5A37B421 for ; Tue, 5 Feb 2002 16:27:09 -0800 (PST) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id g160DDx19684 for bugs@freebsd.org; Tue, 5 Feb 2002 16:13:13 -0800 (PST) (envelope-from dg) Date: Tue, 5 Feb 2002 16:13:13 -0800 From: David Greenman To: bugs@freebsd.org Subject: [legg@iastate.edu: Serious exception in FreeBSD found] Message-ID: <20020205161313.B19463@nexus.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ----- Forwarded message from Tim Legg ----- Delivered-To: freebsd-questions@freebsd.org Date: Tue, 5 Feb 2002 17:58:29 -0600 (CST) From: Tim Legg To: freebsd-questions@freebsd.org Subject: Serious exception in FreeBSD found List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Precedence: bulk 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 ----- End forwarded message ----- -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com President, Download Technologies, Inc. - http://www.downloadtech.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message