summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorben <ben@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2002-11-22 08:06:45 +0000
committerben <ben@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2002-11-22 08:06:45 +0000
commite4d46b43f475ddbc14f23933210a435e1255cf65 (patch)
tree725afe122518637b9b020817b845afc371542d71
parenta01ac62db2729d257f6682ffefe991dd0ad90083 (diff)
downloadrdiff-backup-e4d46b43f475ddbc14f23933210a435e1255cf65.tar.gz
Various changes
git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@230 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
-rw-r--r--rdiff-backup/CHANGELOG7
-rw-r--r--rdiff-backup/FAQ-body.html17
-rw-r--r--rdiff-backup/TODO3
-rw-r--r--rdiff-backup/rdiff-backup.16
4 files changed, 30 insertions, 3 deletions
diff --git a/rdiff-backup/CHANGELOG b/rdiff-backup/CHANGELOG
index a663f3f..8bd7cee 100644
--- a/rdiff-backup/CHANGELOG
+++ b/rdiff-backup/CHANGELOG
@@ -1,3 +1,10 @@
+New in v0.11.1 (2002/12/??)
+---------------------------
+
+Fixed bug with the --{include|exclude}-globbing-filelist options
+(reported by Claus Herwig).
+
+
New in v0.11.0 (2002/10/05)
---------------------------
diff --git a/rdiff-backup/FAQ-body.html b/rdiff-backup/FAQ-body.html
index b493609..ee8f968 100644
--- a/rdiff-backup/FAQ-body.html
+++ b/rdiff-backup/FAQ-body.html
@@ -25,6 +25,9 @@ session statistics and directory statistics files?</a></li>
<li><a href="#bwlimit">Is there some way to limit rdiff-backup's
bandwidth usage, as in rsync's --bwlimit option?</a></li>
+<li><a href="#leak">How much memory should rdiff-backup use? Is there a
+memory leak?</a></li>
+
</ol>
<h3>Questions and Answers</h3>
@@ -375,7 +378,21 @@ rdiff-backup to exceed it for significant periods.</li>
Another option is to limit bandwidth at a lower (and perhaps more
appropriate) level. Adam Lazur mentions <a
href="http://lartc.org/wondershaper/">The Wonder Shaper</a>.
+</li>
+
+<a name="leak">
+<li><strong>How much memory should rdiff-backup use? Is there a
+memory leak?</strong>
+
+<p>The amount of memory rdiff-backup uses should not depend much on
+the size of directories being processed. Keeping track of hard links
+may use up memory, so if you have, say, hundreds of thousands of files
+hard linked together, rdiff-backup may need tens of MB.
+<p>If rdiff-backup seems to be leaking memory, it is probably because
+it is using an early version of librsync. <strong>librsync 0.9.5
+leaks lots of memory.</strong> Version 0.9.5.1 should not leak and is
+available from the rdiff-backup homepage.
</li>
</ol>
diff --git a/rdiff-backup/TODO b/rdiff-backup/TODO
index 161f299..02ac5b2 100644
--- a/rdiff-backup/TODO
+++ b/rdiff-backup/TODO
@@ -9,6 +9,9 @@ etc., are skipped.
Look at error code, make sure filename is always mentioned (see Knops
email).
+Add --list-files-changed-between or similar option, to list files that
+have changed between two times
+
---------[ Medium term ]---------------------------------------
Add --dry-run option (target for v1.1.x)
diff --git a/rdiff-backup/rdiff-backup.1 b/rdiff-backup/rdiff-backup.1
index 2597fa4..3a1efe7 100644
--- a/rdiff-backup/rdiff-backup.1
+++ b/rdiff-backup/rdiff-backup.1
@@ -229,12 +229,12 @@ the directory statistics file.
.TP
.B --parsable-output
If set, rdiff-backup's output will be tailored for easy parsing by
-computers, instead of clarity for humans. Currently this only applies
-when listing increments using the
+computers, instead of convenience for humans. Currently this only
+applies when listing increments using the
.B -l
or
.B --list-increments
-switches.
+switches, where the time will be given in seconds since the epoch.
.TP
.B --print-statistics
If set, summary statistics will be printed after a successful backup