Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!EE.ECN.PURDUE.EDU!bevis
From: bevis@EE.ECN.PURDUE.EDU (Jeff Bevis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Clean way to kill AUX: cli
Message-ID: <8910232238.AA18077@en.ecn.purdue.edu>
Date: 23 Oct 89 22:38:17 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Purdue University Engineering Computer Network
Lines: 17

I don't intend to start another hyper-extended round of resource-tracking
discussions, but I would like to pose a small(?) question.  If one were to
keep track of process resources, what would one be keeping track of, aside
from memory, message ports, file locks, and, perhaps, semaphores?  I've not
really given this much thought, but I would like to know what the scope of
full resource tracking is.

I don't want this post to precipitate more 'we can't do that on the Amiga.'
replies;  I'm not debating that.  I'm just wondering what everyone wishes
they could have the OS tracking for them... (aside from the aforementioned).
It might be best if responses were emailed to me, since this is an old topic.
Thanks for the enlightenment in advance.

+-----------------------------------------------------------------------------+
| Jeff Bevis  (bevis)				     "But I don't like spam!" |
| en.ecn.purdue.edu / ei.ecn.purdue.edu	     Give me Amiga or nothing at all. |
+-----------------------------------------------------------------------------+