From owner-freebsd-hackers  Tue Mar  5 17:53:09 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA16074
          for hackers-outgoing; Tue, 5 Mar 1996 17:53:09 -0800 (PST)
Received: from zip.io.org (root@zip.io.org [198.133.36.80])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA16069
          for <hackers@freebsd.org>; Tue, 5 Mar 1996 17:53:06 -0800 (PST)
Received: (from taob@localhost) by zip.io.org (8.6.12/8.6.12) id TAA22723; Tue, 5 Mar 1996 19:56:18 -0500
Date: Tue, 5 Mar 1996 19:56:17 -0500 (EST)
From: Brian Tao <taob@io.org>
To: Jon Loeliger <jdl@jdl.com>
cc: Joe Greco <jgreco@brasil.moneng.mei.com>, hackers@freebsd.org
Subject: Re: Latest 2.1R panic. Hmm.
In-Reply-To: <199602282134.PAA07301@chrome.jdl.com>
Message-ID: <Pine.BSF.3.91.960305195210.16822A-100000@zip.io.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
Precedence: bulk

On Wed, 28 Feb 1996, Jon Loeliger wrote:
> 
> And, on the other hand, it's kinda cool NOT to too:
> 
> This is command 8464 in one window:
>     chrome 8464 % ps auxwww | grep bin/emacs
>     jdl        405  0.0  9.8  5956 1380  v0  SN    4Feb96   29:03.22 /usr/
>     local/bin/emacs -display :0 -geometry 80x50+675+0 -f server-start

    What sort of limits might we be running into with long-lived
processes?  The oldest one I have on our machines is our IRC server:

# date
Tue Mar  5 19:53:52 EST 1996
# ps aux | head -2
USER       PID %CPU %MEM   VSZ  RSS  TT  STAT STARTED       TIME COMMAND
andrew    6069  1.7 26.9 18268 17068  ??  SN    7Feb96  2834:23.83 /usr/ircd/ircd

    I imagine the CPU time will eventually wrap around, but other than
that, the other bits of information should remain valid indefinitely.
That's almost 2 days' worth of CPU time.  :)
--
Brian Tao (BT300, taob@io.org)
Systems Administrator, Internex Online Inc.
"Though this be madness, yet there is method in't"