summaryrefslogtreecommitdiff
path: root/rdiff-backup/rdiff-backup.1
diff options
context:
space:
mode:
authorben <ben@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2002-05-10 23:19:07 +0000
committerben <ben@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2002-05-10 23:19:07 +0000
commit78d63fa4138984f39b7ac9265d8e86827a2861f2 (patch)
tree747bc61ccb915a2e47d6ead59f29014d711c5718 /rdiff-backup/rdiff-backup.1
parent40fd4661d4b2a0fd2b2517408d4c5982474b2105 (diff)
downloadrdiff-backup-78d63fa4138984f39b7ac9265d8e86827a2861f2.tar.gz
Added info on filename length bug
git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@74 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
Diffstat (limited to 'rdiff-backup/rdiff-backup.1')
-rw-r--r--rdiff-backup/rdiff-backup.18
1 files changed, 6 insertions, 2 deletions
diff --git a/rdiff-backup/rdiff-backup.1 b/rdiff-backup/rdiff-backup.1
index 82b6f11..5392b9c 100644
--- a/rdiff-backup/rdiff-backup.1
+++ b/rdiff-backup/rdiff-backup.1
@@ -712,8 +712,12 @@ handled correctly on systems with non-standard mknod syntax.
.PP
When an rdiff-backup session fails (for instance if a remote
connection is lost), rdiff-backup tries to save the session so it can
-be resumed later. Apparently, depending on how the rdiff-backup
-session fails, later sessions cannot be resumed properly.
+be resumed later. Apparently sometimes, depending on how the
+rdiff-backup session fails, later sessions cannot be resumed properly.
+.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.
.SH AUTHOR
Ben Escoto <bescoto@stanford.edu>