Hello Wayne,
--Am Mittwoch, 25. August 2004 9:03 Uhr -0700 schrieb Wayne Davison
<[EMAIL PROTECTED]>:
What would you think of a tie-break for identical names that depended on
some other attribute of the files? Such as newest file wins? That
would be quite easy to add and would be deterministic,
Hi Wayne,
Sorry to disturb u again,
but now i have one more very small problem.
we need not to supply the password on command line
everytime,
when we will use rsync for transferring files from one
m/c to another,i want to fix login name as well as
passord for a particular m/c.
I try out the option
Hi Wayne,
Sorry to disturb u again,
but now i have one more very small problem.
we need not to supply the password on command line
everytime,
when we will use rsync for transferring files from one
m/c to another,i want to fix login name as well as
passord for a particular m/c.
I try out the option
https://bugzilla.samba.org/show_bug.cgi?id=1660
--- Additional Comments From [EMAIL PROTECTED] 2004-08-25 14:03 ---
Wayne,
This is the way BackupPC (using File::RsyncP) invokes the client side
of rsync. This is perl code that emulates one side of the rsync
connection, and the real r
On Wed, Aug 25, 2004 at 08:44:15AM +0200, Dirk Pape wrote:
> Since in our scenario using rsync we rely on deterministic behaviour
What would you think of a tie-break for identical names that depended on
some other attribute of the files? Such as newest file wins? That
would be quite easy to add
https://bugzilla.samba.org/show_bug.cgi?id=1660
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Additional Comments
On Wed 25 Aug 2004, Dirk Pape wrote:
> --Am Mittwoch, 25. August 2004 10:03 Uhr +0200 schrieb Paul Slootman
> <[EMAIL PROTECTED]>:
>
> >What I'm wondering is why it's a problem that the same file is
> >"randomly" copied from one of a number of sources, if indeed it is the
> >same file. The result
Hallo Paul,
--Am Mittwoch, 25. August 2004 10:03 Uhr +0200 schrieb Paul Slootman
<[EMAIL PROTECTED]>:
What I'm wondering is why it's a problem that the same file is
"randomly" copied from one of a number of sources, if indeed it is the
same file. The resulting destination will be the same, right?
Seems fine, using inodes to sort out duplicates is a great idea. I
suppose using hashes won't give much speedup here, since quantity of
directories is not known beforehand. I will apply and test the patch
today, thanks!
Wayne Davison wrote:
On Fri, Aug 20, 2004 at 04:50:45PM +0400, Ivan S. Mani
On Wed 25 Aug 2004, Dirk Pape wrote:
> some time ago I reported a bug, where we saw indeterministic behaviour of
> rsync (all versions since 2.5), when having the same file appearing in
> multiple sources. Sometimes the file in the first source was copied, other
> times the file was copied from
On Fri, Aug 20, 2004 at 04:50:45PM +0400, Ivan S. Manida wrote:
> Or please kick me in the right direction for a workaround which would
> make --keep-dirlinks consider sane symlinks only.
Seems like the only good solution for this is to keep track of the
device and inode of all the dirs we visit
11 matches
Mail list logo
