Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!karl
From: karl@sugar.hackercorp.com (Karl Lehenbauer)
Newsgroups: comp.sys.amiga.tech
Subject: Re: resource tracking
Keywords: Discipline, discipline
Message-ID: <5156@sugar.hackercorp.com>
Date: 16 Feb 90 02:33:58 GMT
References: <355.25C92297@weyr.FIDONET.ORG> <926@tardis.Tymnet.COM> <352@amgraf.UUCP>
Reply-To: karl@sugar.hackercorp.com (Karl Lehenbauer)
Organization: Sugar Land Unix - Houston
Lines: 18

In article <352@amgraf.UUCP> huver@amgraf.UUCP (Huver) writes:
>Not so fast.  UNIX IPC provides posting/sharing preset and/or allocated
>memory blocks among processes (that don't have to be forked in the same
>family).  Such m/calloc'd memory certainly cannot be freed "with no problem".

Regular memory allocation calls probably happen ten thousand times more often
than IPC stuff.  IPC is the exception, and it is there specifically to allow
sharing between process and as such, sure, you have to have some plan for
cleaning up.  But the normal Unix program can dump core with impunity and
still get its normal memory freed without doing anything, which is nice.

Yeah, not having resource tracking on the Amiga is a bummer, but I've
gotten used to it, developed some tools, etc, so it's not so bad.

-- 
-- uunet!sugar!karl	"As long as there is a legion of superheros, all else
--			 can surely be made right." -- Sensor Girl
-- Usenet access: (713) 438-5018