Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!rutgers!pyrnj!hhb!bvk
From: bvk@hhb.UUCP (Brett Kuehner)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Zoo problems (disk thrashing)
Summary: Happens to me, too
Message-ID: <171@hhb.UUCP>
Date: 26 Jan 89 21:18:37 GMT
References: <2169@van-bc.UUCP>
Organization: HHB Systems, Mawah, NJ
Lines: 27

In article <2169@van-bc.UUCP> lphillips@lpami.wimsey.bc.ca (Larry Phillips)
writes:
> 
> Um... I'm running the release version of 1.3 and I have my stack set to
> 30000, and I occasionly get zoo seemingly just looping while trying to read
> a zoo archive. It doesn't crash (I can break it), but it is annoying to
> have to the zoo archive to ram: to look at it. I don't recall offhand what
> else I have running in the background that may effect things.
> 
> 	fred

Is this when your zoo archive is in a directory with a lot of files in it? I
have a directory on my HD with about 50 files in it. If I do a
"zoo l foo.zoo", where foo.zoo is in that directory, zoo appears to thrash
on the drive a lot, possibly reading in the name of each file in the
HD directory (and very slowly). It will eventually list the archive, though.
This happened with zoo 1.42, and I believe it happens with zoo 2.00 as well
(I'll have to make sure that's what I ran). The amount of disk thrashing
that goes on is definitely related to the number of files in the HD directory.
Could someone with the source check out why this might happen? (or is this
known and fixed in 2.01?)

		Brett
--
Brett Kuehner
...!princeton!hhb!bvk
bvk%hhb@princeton.EDU