From 1986e8f698b346f0ff35b272aeea0258a6c640b7 Mon Sep 17 00:00:00 2001 From: owsla Date: Thu, 8 Jan 2009 00:17:52 +0000 Subject: Update FAQ git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/branches/r1-2@1010 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109 --- rdiff-backup/FAQ-body.html | 19 ++++++++++++++++--- rdiff-backup/rdiff_backup/SetConnections.py | 4 +++- 2 files changed, 19 insertions(+), 4 deletions(-) diff --git a/rdiff-backup/FAQ-body.html b/rdiff-backup/FAQ-body.html index 4df950d..4995bc9 100644 --- a/rdiff-backup/FAQ-body.html +++ b/rdiff-backup/FAQ-body.html @@ -28,6 +28,7 @@ how much is required? What is the problem if rdiff-backup says
  • What does "touple index out of range" mean?
  • What does "IO Error: CRC check failed" mean?
  • What does "AssertionError: Bad index order" mean?
  • +
  • How can rdiff-backup use UTC as the timzeone?
  • Questions and Answers

      @@ -112,9 +113,12 @@ a full explanation of why this happens see this post to the mailing list:
    1. Can I backup files to a CIFS or smbfs mount?

      You can certainly try! Using a CIFS or smbfs mount as the mirror directory has been troublesome for some users because of the wide variety of Samba configurations. If possible, the best solution is always -to use rdiff-backup over SSH in the default configuration. Under both Linux and Mac OS X, smbfs seems to -be working quite well. However, it has a 2 GB file limit and is deprecated on Linux. CIFS users sometimes -experience one of these common errors:

      +to use rdiff-backup over SSH in the default configuration. Using rdiff-backup in the default configuration +is also guaranteed to be faster because there is lower network utilization. Rdiff-backup uses +the rsync algorithm to minimize the amount of bandwidth consumed. By using smbfs or CIFS, the complete file +is transferred over the network.

      +

      Under both Linux and Mac OS X, smbfs seems to be working quite well. However, it has a 2 GB file limit and is +deprecated on Linux. CIFS users sometimes experience one of these common errors:

      • rdiff-backup fails to run, printing an exception about "assert not upper_a.lstat()" failing. This can be resolved by unmounting the share, running the following command as root:
        @@ -428,4 +432,13 @@ list.

      • +
      • How can rdiff-backup use UTC as the timezone? + +

        Like other Unix and Python programs, rdiff-backup respects the TZ environment variable, which can +be used to temporarily change the timezone. On Unix, simply set TZ=UTC either in your shell, or on the +command line used to run rdiff-backup. On Windows, the command USE TZ=UTC sets the %TZ% +environment variable, and can be used either in a batch script, or at the DOS prompt.

        + +
      • +
    diff --git a/rdiff-backup/rdiff_backup/SetConnections.py b/rdiff-backup/rdiff_backup/SetConnections.py index 465fcb3..d61a65f 100644 --- a/rdiff-backup/rdiff_backup/SetConnections.py +++ b/rdiff-backup/rdiff_backup/SetConnections.py @@ -247,7 +247,9 @@ def test_connection(conn_number): conn = Globals.connections[conn_number] try: assert conn.Globals.get('current_time') is None - assert type(conn.os.getuid()) is int + assert type(conn.os.name) is str + if (conn.os.name != 'nt'): + assert type(conn.os.getuid()) is int version = conn.Globals.get('version') except: sys.stderr.write("Server tests failed\n") -- cgit v1.2.1