[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2011-02-12 Thread Andreas Olsson
Marking as resolved, as the rsnapshot packages does depend on liblchown- perl as of rsnapshot 1.3.1-1 (maverick). Regarding enabling cmd_cp by default, I would say that that is part of a more general approach to rsnapshot.conf, such as covered by bug #278998. I have contacted the Debian rsnapshot

[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2011-01-23 Thread Xavier Robin
It is better to enable the cmd_cp line. The conf file clearly states it is better enabling it than installing this perl module. I think this patch for rsnapshot.conf.default.in would fix it. ** Patch added: Patched rsnapshot.conf.default.in

[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2011-01-23 Thread Brian Murray
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/340671 Title: WARNING: Could not lchown() symlink ... -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2010-11-17 Thread Heiko Ettelbrück
Maybe that's just because only hourly (in your configuration) really backs up files from your productive machine/volume, while the higher backup levels like daily and weekly just clone the hard links from the parent level (e.g. daily.0 is a clone of hourly.0). See the man page of rsnapshot:

[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2010-11-17 Thread Håkon A . Hjortland
Xavier, Heiko: I think the other backups than hourly just involve folder renaming. That's why they won't have any lchown problems. From my /var/log/rsnapshot.log: [17/Nov/2010:03:30:01] /usr/bin/rsnapshot daily: started [17/Nov/2010:03:30:01] echo 11101 /var/run/rsnapshot.pid

[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2010-11-05 Thread Xavier Robin
Quite surprisingly it affects only hourly backups. My daily and weekly backups run without warnings. -- WARNING: Could not lchown() symlink ... https://bugs.launchpad.net/bugs/340671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2010-07-27 Thread Mark Foster
Please add depends for liblchown-perl, or adjust the rsnapshot.conf defaults to link_dest 1 and cmd_cp /bin/cp as described earlier. -- WARNING: Could not lchown() symlink ... https://bugs.launchpad.net/bugs/340671 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2009-12-14 Thread Derek Simkowiak
Me too. (Add the liblchown-perl dependency please.) -- WARNING: Could not lchown() symlink ... https://bugs.launchpad.net/bugs/340671 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2009-12-07 Thread Jorgen Austvik
I was just about to file the same bug, and can confirm Håkon's findings re liblchown-perl, and think adding a dependency would be good. I have also updated my config file based on Håkon's suggestions above. -- WARNING: Could not lchown() symlink ... https://bugs.launchpad.net/bugs/340671 You

[Bug 340671] Re: WARNING: Could not lchown() symlink ...

2009-06-14 Thread Håkon A . Hjortland
Perl lchown package in Jaunty: liblchown-perl Installing this package stopped the rsnapshot lchown-warnings for me. It should probably be a dependency of the rsnapshot package. Perhaps a better alternative than to use rsnapshot's internal copy-function is to use the cp binary. From