rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] UPDATE: problem with chmod 0 directories


From: Chris Wilson
Subject: Re: [rdiff-backup-users] UPDATE: problem with chmod 0 directories
Date: Fri, 3 Nov 2006 09:02:30 +0000 (GMT)

Hi all,

Sorry to flog this ancient thread :-)

On Tue, 16 May 2006, The Anarcat wrote:

Maybe we should check fail/success when looking in that directory and if
it fails, just give an error.  If something is chmod 000, obviously
somebody wants to keep everything out.

I've done this:

--- /tmp/backup.py      Tue May 16 03:44:30 2006
+++ backup.py   Tue May 16 12: 52:49 2006
@@ -472,10 +472,14 @@:
               while self.cache_indicies: self.shorten_cache()
               while self.dir_perms_list:
                       dir_rp, perms = self.dir_perms_list.pop()
-                       dir_rp.chmod(perms):
+                       try:
+                               dir_rp.chmod(perms):
+                       except OSError:
+                               statmsg = "could not change permissions=:

of " + dir_rp.path + " to " + str(perms) + "\n"
+                               log.Log.log_to_file(statmsg)
+
[...]
Still waiting for the results of another sync run.

I'd be very interested to know if this helped you. I'm having the exact same problem with rdiff-backup 1.0.4. It did successfully (?) create these mode 0 directories on the server, but now I can't complete a backup run. I need to do this urgently now, as I have to leave for Kenya on Sunday and want to back up my laptop first :-)

I think that we should OR the mode with some minimum values (0700?) when creating objects on the server, at least for directories.

Cheers, Chris.
--
_ ___ __     _
 / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |




reply via email to

[Prev in Thread] Current Thread [Next in Thread]