In this commit you put "extraneous hard-linked files". I find this
confusing because the hard-linked entries may have been created by
rsync itself. I think the previous version is better. Or you could put
"If there are files that are hard-linked at the destination but not at
the origin".
--
Please
Rsync version 3.0.8pre1 is now available for release testing. This is
a bug-fix release.
Please test this new release and send email to the rsync mailing list
with any questions, comments, or bug reports.
To see a full summary of the changes since 3.0.7, visit this link:
http://rsync.samba.or
https://bugzilla.samba.org/show_bug.cgi?id=6936
way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=6694
way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=6542
way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5680
way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=7959
--- Comment #1 from way...@samba.org 2011-02-22 10:58 CST ---
I believe you mean by "go on" that it will hang? (Rather than go on to the
next command?) If so, you should check to see what rsync is doing. For
instance, run it under str
https://bugzilla.samba.org/show_bug.cgi?id=7884
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=7953
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=7939
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=7667
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=7246
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=7129
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5939
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=7425
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Tue 22 Feb 2011, Xabi Vazquez wrote:
>
> thanks for your answer, but I can't run rsync as ad daemon on the
> machine. What it's amazing is error happens always in the same dir, and I
> have no problem with other ones. Any other possible solution?
Try changing the order of the rsync run
Hi Paul:
thanks for your answer, but I can't run rsync as ad daemon on the
machine. What it's amazing is error happens always in the same dir, and I have
no problem with other ones. Any other possible solution?
Why other directories are syncing but this one? Why running the comma
On Tue 22 Feb 2011, Xabi Vazquez wrote:
> [Tue Feb 22 02:51:34 CET 2011] /usr/bin/rsync -az --delete --numeric-ids
> --relative --delete-excluded --rsh=/usr/bin/ssh root@server1:/opt/clamav
> /data/backups/server1
> ssh: connect to host mx2.ecliente.com port 22: Connection timed out
ssh itself
Hi there:
I'm doing a backup of some of my machines via rsync, and I have the next
problem:
--
[Tue Feb 22 02:51:13 CET 2011] /usr/bin/rsync -az --delete --numeric-ids
--relative --delete-excluded --rsh=/usr/bin/ssh root@server1:/var/spool/exim
/data/backups/server1
[Tue Feb 22
19 matches
Mail list logo