CRONEJP@UREGINA1.BITNET (Jonathan Crone) (04/29/89)
I'm running Zoo V2.00 and although i can't believe it, Zoo has been running for 20 minutes, and STILL hasn't even gotten around to starting COMPRESSING.... zoo is running in a directory with approximately 60 files in it of varying lengths and sizes... there are 6 .c files, 3 .h files, and a few other files, directly referenced the following command line was used, and ITS STILL CHEWING ON IT!!!!!! zoo -move cc cc.c config.h dstr.? list.? err.c op.? options.? all in all, about 12 files.. What the heck is going on.... Although i didn't realize it at the time, about an hour ago, i did something similar, only with all the file names directly provided, and it ran forever as well, i ended up CTRL Cing and doing it in ram (I thought that Zoo had crashed) This is a a FFS partition and cc.zoo already existed... JpC -------------------------------------------------------------------- Jonathan P. Crone CRONEJP@UREGINA1.BITNET cronejp@mcl.UUCP If Einstein could have used a computer, he would have used an Amiga...
grwalter@watmath.waterloo.edu (Fred Walter) (04/29/89)
In article <8904290204.AA00910@jade.berkeley.edu> CRONEJP@UREGINA1.BITNET (Jonathan Crone) writes: >I'm running Zoo V2.00 and although i can't believe it, >Zoo has been running for 20 minutes, and STILL hasn't even >gotten around to starting COMPRESSING.... >zoo is running in a directory with approximately 60 files in it >of varying lengths and sizes... > >zoo -move cc cc.c config.h dstr.? list.? err.c op.? options.? > >all in all, about 12 files.. This is a known zoo 2.0 (and earier versions) problem. It does wildcarding in a .. very slow .. way, and thus if you have lots'a files (60 counts as lots) it takes a while. Multiply the time it takes to handle one filename by 12, and I can believe it'd take > 20 minutes. Solutions : be very patient; execute zoo from a directory where there aren't many files; OR wait until the version of zoo with this fixed turns up :-) fred
randy@jato.Jpl.Nasa.Gov (Randy Hammock) (04/30/89)
>>I'm running Zoo V2.00 and although i can't believe it, >>Zoo has been running for 20 minutes, and STILL hasn't even >>gotten around to starting COMPRESSING.... >>zoo is running in a directory with approximately 60 files in it >>of varying lengths and sizes... >This is a known zoo 2.0 (and earier versions) problem. It does wildcarding >in a .. very slow .. way... If you find that slow, you should try: zoo v <filename> on a directory that has a fair number of files. I thought zoo had gone berserk and was trying to destroy my hard disk. Once I realized what was going on, I either grin and bear the time or let zoo work on files out of ram. -- ============================================================================= Randy Hammock Jet Propulsion Laboratory, Pasadena, CA USENET: randy@jato.jpl.nasa.gov UUCP: ames!elroy!jato!randy =============================================================================
schow@bnr-public.uucp (Stanley Chow) (05/01/89)
In article <1215@jato.Jpl.Nasa.Gov> randy@jato.UUCP (Randy Hammock) writes: >>>I'm running Zoo V2.00 and although i can't believe it, >>>Zoo has been running for 20 minutes, and STILL hasn't even >>>gotten around to starting COMPRESSING.... >>>zoo is running in a directory with approximately 60 files in it >>>of varying lengths and sizes... > >>This is a known zoo 2.0 (and earier versions) problem. It does wildcarding >>in a .. very slow .. way... > >If you find that slow, you should try: zoo v <filename> on a directory >that has a fair number of files. I thought zoo had gone berserk and was >trying to destroy my hard disk. Once I realized what was going on, I either >grin and bear the time or let zoo work on files out of ram. Hmm, I have been using zoo 2.00 for a while and have never noticed any problem along this line. In fact, I just tried: zoo a ram:ttt * zoo a ram:ttt f*k* in my utilities directory with about 60 files. [Btw, f*k* is for FlamKey, not anything nasty.] Zoo starts doing things within a few seconds. I do have a lot of buffers, may be that makes a difference? Stanley Chow ..!utgpu!bnr-vpa!bnr-fos!schow%bnr-public Bitnet: schow@BNR.CA.BITNET Disclaimer: I am not a biologist, so don't believe me when I start talking about zoo's.
dca@toylnd.UUCP (David C. Albrecht) (05/10/89)
In article <25674@watmath.waterloo.edu>, grwalter@watmath.waterloo.edu (Fred Walter) writes: > In article <8904290204.AA00910@jade.berkeley.edu> CRONEJP@UREGINA1.BITNET (Jonathan Crone) writes: > >I'm running Zoo V2.00 and although i can't believe it, > >Zoo has been running for 20 minutes, and STILL hasn't even > >gotten around to starting COMPRESSING.... > >zoo is running in a directory with approximately 60 files in it > >of varying lengths and sizes... > > > >zoo -move cc cc.c config.h dstr.? list.? err.c op.? options.? > > > >all in all, about 12 files.. > > This is a known zoo 2.0 (and earier versions) problem. It does wildcarding > in a .. very slow .. way, and thus if you have lots'a files (60 counts as > lots) it takes a while. Multiply the time it takes to handle one filename > by 12, and I can believe it'd take > 20 minutes. Solutions : be very > patient; execute zoo from a directory where there aren't many files; OR > wait until the version of zoo with this fixed turns up :-) > Really? It wasn't until I installed FFS on my hard drive that I noticed this infinite loop simulation behavior It seems awfully coincidental that it only began happening after the switch. Yes it is a large directory, but it was large before the conversion also. I have taken to doing a 'list >pipe:files (wildcards) quick' in one cli window and a 'zoo <pipe:files aI output_file' in the other, it's gross but it works. U s e n e t f o o d David Albrecht