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

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

Re: [rdiff-backup-users] bug?: uid of symlinks restored incorrectly


From: mailinglist
Subject: Re: [rdiff-backup-users] bug?: uid of symlinks restored incorrectly
Date: Thu, 25 May 2006 18:53:53 -0400
User-agent: Thunderbird 1.5.0.2 (Macintosh/20060308)

Andrew Ferguson wrote, On 03/05/06 00:36:
    Warning: lchown missing, cannot change ownership of symlink /
    
rdiff-backup 1.0.4
Redhat 9 (2.4.32)
Python 2.2.2 (#1, Feb 24 2003, 19:13:11)
    

Python 2.2 does not support the lchown() system call. I think version
2.3 does support it (2.4.3 is the latest). Perhaps you can find a more
recent version of Python for your distribution? There have been some
security fixes since 2.2.2 anyway.

Without the lchown() system call support, rdiff-backup cannot change the
owner of the symlinks upon restore. So what you see is (unfortunately)
expected.
I've upgraded my two servers to Python 2.4.3. Now everything works flawless with brand new destination directories or new symbolic links in pre-Python 2.4.3 backups. But under pre-Python 2.4.3 backups, existing symbolic links uid/gid don't get updated (still root/root). Is there a way to force *higher level* of comparison and get the uid/gid updated in pre-Python 2.4.3 backup? (I've try to recreate symbolic links, change symbolic link uid/gui and/or target uid/gui... w/o any luck...)

Thanks!

Ben.

reply via email to

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