Re: [rdiff-backup-users] rdiff-backup + chirp : symlinked_file problem

[Andrew Ferguson]

On Dec 2, 2008, at 8:25 PM, Julien Poffet wrote:

OSError: [Errno 13] Permission denied: '/tmp/bck/131.243.51.142/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2'


However if I list the content of the target backup directory in the host I have the following result:

address@hidden:~/vml/backup$ ls -l rdiff-backup-data/rdiff-backup.tmp.0/
total 8
-rw------- 2 popei popei    0 2008-12-02 17:12 hardlinked_file1
drwx------ 2 popei popei 4096 2008-12-02 17:12 hl
lrwxrwxrwx 1 popei popei   72 2008-12-02 17:12 symlinked_file2 -> /bck/131.243.51.142/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file1

It seems that the symlinked_file2 is set to a wrong directory path. It should be /tmp/bck/131... and so on.

Hi Julien,

Thanks for reporting this issue. The filesystem test which produced that errant symlink needed to be cleaned-up, which I have done in CVS.

However, what you have encountered is also a bug in the chirp filesystem. All other Unix filesystems are capable of deleting a broken symlink. Chrip should either delete broken symlinks, or prevent you from creating them in the first place (allowing users to create files they can't delete is generally bad practice. :-)

Andrew