| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Changes since version 1.0.32:
- Tarsnap now caches archive metadata blocks in RAM, typically
providing a 5x - 10x speedup and reduction in bandwidth usage
in the "fsck" operation and when deleting a large number of
archives at once.
- Tarsnap's internal "chunk" metadata structure is now smaller,
providing a ~10% reduction in usage on 32-bit machines and a
~30% reduction in memory usage on 64-bit machines.
- Tarsnap's --newer* options now correctly descend into old
directories in order to look for new files. (But note that
tarsnap's snapshotting makes these options unnecessary in
most situations.)
- Multiple minor bug fixes and cleanups.
Changes since version 1.0.31:
- A bug affecting the handling of the --nodump option on Linux
(and in most cases rendering it inoperative) is fixed.
- A workaround has been added for a compiler bug in OS X 10.7 (Lion).
- The NetBSD "kernfs" and "ptyfs" filesystems are now excluded
from archival by default.
|
|
Changes since version 1.0.30:
- A race condition in key generation has been fixed which could
allow a newly-generated key file to be read by another local
user if the key file is being generated in a world-readable
directory and the user running tarsnap-keygen has a umask other
than 0066.
- A bug in key generation has been fixed which could allow a
newly-generated key file to be read by another local user
if they key file is being generated in a world-writable
directory (e.g., /tmp).
- Tarsnap now supports Minix.
- Tarsnap now ignores blank lines in key files; line-buffers
its output (which makes tarsnap --list-archives | foo more
responsive); and prints a progress indicator during tarsnap --fsck.
- Multiple minor bug fixes.
|
|
Changes since version 1.0.29:
A bug fix in the handling of readdir errors; in earlier versions,
it was theoretically possible for a failing hard drive or other
errors in reading directories to result in files being silently
omitted from an archive.
Several bug fixes relating to the handling of @archive directives
with mtree files.
A bug fix to prevent cache directory corruption resulting in
tarsnap failing if it was interrupted at exactly the right
(wrong) moment in its operation.
A bug fix to correctly handle ~ in tarsnap -s path substitutions.
Many more minor bug fixes.
|
|
tarsnap from security to sysutils.
|
