Changes between Version 18 and Version 19 of FAQ

Timestamp:

18/09/2009 18:31:15 (12 months ago)

Author:

chris

Comment:

--

FAQ

@@ -45 +45 @@
 This seems to happen with small file changes, especially on Gentoo in /etc (see above).
 
-It seems that Gentoo may touch configuration files at the same time that it creates a new version for future merges (reported by Ben Bennett on 13/03/2007). We have not been able to reproduce this, but the case that he presented is a problem.
+It seems that Gentoo may touch configuration files at the same time that it creates a new version for future merges (reported by Ben Bennett on 13/03/2007). This resets the timestamp of the modified file back to the timestamp of the original, unmodified file. We have not been able to reproduce this, but the case that he presented is a problem.
 
-If a file is modified or replaced by another file with the same modification time, Box Backup will ignore the fact that the file has changed.
+If a file is modified or replaced by another file with the same modification time, Box Backup will ignore the fact that the file has changed. Therefore, Box Backup does not back up the updated configuration files.
 
 This is arguably a bug in Gentoo, which affects other incremental backup solutions as well, but we are working on a fix for this.
@@ -58 +58 @@
 * ``MaximumDiffingTime reached - suspending file diff``
 
-This probably means that a large file was being diffed, that it took too long (more than MaximumDiffingTime seconds) and that the entire file was uploaded instead. If the file really is large, you can probably reduce bandwidth usage by increasing the MaximumDiffingTime value on the client.
+This probably means that a large file was being diffed, that it took too long (more than :trac:`MaximumDiffingTime` seconds) and that the entire file was uploaded instead. If the file really is large, you can probably reduce bandwidth usage by increasing the :trac:`MaximumDiffingTime` value on the client.
 
-Try enabling the LogAllFileAccess option on the client, which should report which files were uploaded, and whether they were completely
+Try enabling the :trac:`LogAllFileAccess` option on the client, which should report which files were uploaded, and whether they were completely
 uploaded or as patches. E.g. you should see messages like:
 
@@ -73 +73 @@
  bbackupquery -c /etc/boxbackup/bbackupd.conf -o /tmp/bbackupquery.log -O warning
 
-The ExtendedLogging will probably not help you much unless you're very familiar with the Box Backup protocol. However you can enable it to be logged to a file with the ``-l`` option to ``bbackupquery``.
+The :trac:`ExtendedLogging` option will probably not help you much unless you're very familiar with the Box Backup protocol. However you can enable it to be logged to a file with the ``-l`` option to ``bbackupquery``.
 
 Server Administration Questions