Commit be022168 authored by ben's avatar ben

Various changes


git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup@230 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
parent 1536c173
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)
---------------------------
......
......@@ -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>
......
......@@ -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)
......
......@@ -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
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment