Yes, checking the file size (and also last modification time) certainly adds quite a bit of reliability (and is fast), and that alone may actually be sufficient for the purposes of crazy-duck, but when I mentioned checksum, I used the word as a general term for describing the overall techniques of digital "footprints", digests or signatures. I am using on some of my platforms "checksum" utilities actually implementing a CRC-32 algorithm, where the chances of undetected change are 1 in billions (at least in theory).
| [reply] |
Yes, I tend to use external utilities as well; specifically ones which yield the same results on Linux and Windows. If you have any module suggestions for CRC-32 I would be interested in stealing from your experience base. :-)
| [reply] |
Well, there are some CRC modules on the CPAN such as String::CRC32 or Digest::CRC, but I have never installed nor used them. I only very occasionally use these digital signature utilities to check file integrity between VMS and Unix platforms (or different Unix platforms), but I never had to do it on a regular basis.
| [reply] |