I have a script which uses Archive::Tar to make a transportable copy of a directory tree. A colleague installed it at a client site and ran out of memory building the archive object before writing it to disk. The Archive::Tar FAQ on CPAN offer some options but they won't fit the case.
My script must be OS agnostic and capable of transferring the directory across platforms in any direction (Windows to Linux, AIX to Windows. etc).
I've looked at Archive::Zip but it's not clear to me where the archive object is built - is it in memory or on disk somewhere BEFORE the $zip->writeToFileNamed method is called? I don't want to rewrite things only to run out of memory all over again!
In reply to Memory limits on Tar modules by murrayn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |