From owner-freebsd-bugs  Sat Dec 30 19:58:14 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA04809
          for bugs-outgoing; Sat, 30 Dec 1995 19:58:14 -0800 (PST)
Received: from mail.mks.com (mks-gate.mks.com [142.77.7.224])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA04801
          for <freebsd-bugs@freebsd.org>; Sat, 30 Dec 1995 19:58:09 -0800 (PST)
Received: from mks.com (giga.mks.com [1.0.0.51])
	by mail.mks.com (8.6.8.1/DEKA-950919b) with SMTP id WAA27242; Sat, 30 Dec 1995 22:57:37 -0500
Received: from mks.com by mks.com (4.1/GIGA-950913a)
	id AA09415; Sat, 30 Dec 95 22:57:36 EST
To: davidg@Root.COM
Cc: freebsd-bugs@freebsd.org
Subject: Re: kern/921: 
In-Reply-To: Your message of "Sat, 30 Dec 1995 19:51:33 -0800."
             <199512310351.TAA01016@corbin.Root.COM> 
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 30 Dec 1995 22:57:35 -0500
Message-Id: <9414.820382255@giga.mks.com>
From: "David J. Fiander" <davidf@mks.com>
Sender: owner-bugs@freebsd.org
Precedence: bulk

>From:  David Greenman <davidg@Root.COM>
>
>   BTW, are you suggesting that rev 1.13/1.14 fixes the problem you're
>reporting?

Not particularly, I was just searching the freebsd-bugs archive
and saw kern/788 covered a related problem.  My problem is
different, however, because it doesn't matter how long a
particular process has been running, but how long the system has
been up (or something).

I figured that it hadn't gotten into RELEASE because it was close
to or after the cut-off for the code-freeze.

- David