Re: mkisofs memory hungry?
> > I got a subtree of 2 million empty files where mkisofs
> > exceeds 2 GB of memory consumption. I never found out
> > wether it would finally end or crash.
> Why? Did you stop it?
I began to fear about the health of my consumer disk.
Hours of extreme disk rattling due to the fight of
stat() and swap (1 GB RAM, 2 GB swap partition).
I was not curious enough to wait for the outcome.
The usual archivers produce 500 MB of uncompressed
result from that subtree within half an hour (slow
enough) and with not more than the usual memory footprint
of a few single MB.
Have a nice day :)