Can we have a proper message/reaction when zip stumbles upon large files?
I think it should complain that the file is too large to be handled
("name not matched"? only Google can decrypt this) and
then *stop* with an error.
The behavior as it is now is missleading and can result in loss of data.
Consider the following scenario:
zip -r archive.zip directory/
where directory contains many files and a few of them are >2G.
Then zip produces archive.zip and a just a warning on to screen.
If there are many files in the directory, the warning is almost unnoticable.
The only way I noticed it was that it was too fast to be true,
like a backup to /dev/null tape in BOFH days :-)
Yet, the consequences could have been much worse if it was running nightly
in crontab and some files growed silently beyond 2G.
Best regards,
Marius
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
