summaryrefslogtreecommitdiff
path: root/rdiff-backup/rdiff-backup.1
diff options
context:
space:
mode:
authorbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2005-11-23 23:16:32 +0000
committerbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2005-11-23 23:16:32 +0000
commit81083cb48d648e0fd96ce3d39df64c71ec15f17b (patch)
treee091bc02d4bfd0219d63095d53c5686d7446c11a /rdiff-backup/rdiff-backup.1
parentb013f40c0c2d1bbbbe1d58208eef9477a791fa0b (diff)
downloadrdiff-backup-81083cb48d648e0fd96ce3d39df64c71ec15f17b.tar.gz
Final (?) too-long-filename bug fix
git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@687 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
Diffstat (limited to 'rdiff-backup/rdiff-backup.1')
-rw-r--r--rdiff-backup/rdiff-backup.19
1 files changed, 0 insertions, 9 deletions
diff --git a/rdiff-backup/rdiff-backup.1 b/rdiff-backup/rdiff-backup.1
index 6f94955..876e203 100644
--- a/rdiff-backup/rdiff-backup.1
+++ b/rdiff-backup/rdiff-backup.1
@@ -961,15 +961,6 @@ automatically (as from
or similar) it is probably a good idea to check the exit code.
.SH BUGS
-rdiff-backup uses the shell command
-.BR mknod (1)
-to backup device files (e.g. /dev/ttyS0), so device files won't be
-handled correctly on systems with non-standard mknod syntax.
-.PP
-Files whose names are close to the maximum length (e.g. 235 chars if
-the maximum is 255) may be skipped because the filenames of related
-increment files would be too long.
-.PP
The gzip library in versions 2.2 and earlier of python (but fixed in
2.3a1) has trouble producing files over 2GB in length. This bug will
prevent rdiff-backup from producing large compressed increments