🚀 go-pugleaf

>In article <1992Sep10.122306.6328@investor.pgh.pa.us> rbp@investor.pgh.pa.us (Bob Peirce #305) writes:
>>In article <1992Sep8.105655.712@macc.wisc.edu> anderson@macc.wisc.edu (Jess Anderson) writes:
>>Neither above poster reveals their standaloneness, but
>
>This is a good point.	I run a standalone system and find jumping to the
>monitor and rebooting to be very quick.  I have done this to restore
>swap space.  I also use it to turn my scanner, which I do not need most
>of the time, on and off.

    Rebooting is NOT an acceptable solution for turnkey systems.

    I've tried to reproduce the problem myself by running every app in
    existance (my swap grows to 20MB) then running librarian (grows to
    25MB), quiting, rerunning it, etc...  but my swap never grows above
    25MB.

    Could the original poster outline the steps he took to generate an ever
    growing swap in more detail?  I'm sure that if something repeatable is
    found the NeXT folk will jump on it.

    I suspect it may be related to the fact that the NeXT caches text
    images (e.g. binaries) after exit and uses generous parameters for the
    cache.  The NeXT also caches files after use (is the executable caching
    a subset of the filecaching or a separate mechanism?)

>--
>Bob Peirce, Pittsburgh, PA	    rbp@investor.pgh.pa.us	   412-471-5320
>venetia@investor.pgh.pa.us [NeXT Mail]  !uunet.uu.net!pitt!investor!rbp [UUCP]

--

    Matthew Dillon	    dillon@Overload.Berkeley.CA.US
    891 Regal Rd.	    uunet.uu.net!overload!dillon
    Berkeley, Ca. 94708     ham: KC6LVW (no mail drop)
    USA 		    Sandel-Avery Engineering (702)831-8000