-- David Nicol <[EMAIL PROTECTED]>
P.S. I included the content-length part just in case anyone knew of a better way to calculate the size a tarball is going to be before it is actually generated...
if you have enough disk space, you could actually create the tarball into a directory that apache is serving as static, then when its done, redirect the user there, instead of running tar twice. Or actually create the tarball, take its size, serve it, then delete it.
That or use gnu cpio which will read/write tarballs and at least exit non-zero for you if the write/extract fails. Unless the stuff being tarballed is already squished (e.g., .gz files or jpeg) you can gzip the output on the fly, at which point the archive and filesystem overhead will get balanced by any squish factor.
-- Steven Lembark 85-09 90th Street Workhorse Computing Woodhaven, NY 11421 [EMAIL PROTECTED] 1 888 359 3508
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
