On Tue, 16 Nov 2010 10:10:36 GMT, edso writes:
>Just for my backlog please, what are your rsync versions?
debian stable has 3.0.2 and testing/squeeze has 3.0.7
>ould you please try to replace the line
>
>self.url_string = "rsync://%s::/%s" % (host, path.lstrip('/:'))
>
>in rsyncbackend.py with
>
>self.url_string = "%s::%s" % (host, path.lstrip(':'))
>
>and check if that works?
that works perfectly, thanks.
one other item re the rsync backend: is there a good reason for
feeding the user part of an rsync uri via the env for rsyncd-module uris?
rsync can deal fine with the username on the commandline for both ssh and rsyncd-modules,
so the code to handle usernames separately seems unnecessary.
regards
az
--
+ Alexander Zangerl + DSA 42BD645D + (RSA 5B586291)
"So instead, I toil through fields of various OSes, planting applications,
spraying patches to catch the bugs, and watching the databases grow."
-- D. Joseph Creighton
On Tue, 16 Nov 2010 10:10:36 GMT, edso writes:
>Just for my backlog please, what are your rsync versions?
debian stable has 3.0.2 and testing/squeeze has 3.0.7
>ould you please try to replace the line
>
>self.url_string = "rsync://%s::/%s" % (host, path.lstrip('/:'))
>
>in rsyncbackend.py with
>
>self.url_string = "%s::%s" % (host, path.lstrip(':'))
>
>and check if that works?
that works perfectly, thanks.
one other item re the rsync backend: is there a good reason for
feeding the user part of an rsync uri via the env for rsyncd-module uris?
rsync can deal fine with the username on the commandline for both ssh and rsyncd-modules,
so the code to handle usernames separately seems unnecessary.
regards
az
--
+ Alexander Zangerl + DSA 42BD645D + (RSA 5B586291)
"So instead, I toil through fields of various OSes, planting applications,
spraying patches to catch the bugs, and watching the databases grow."
-- D. Joseph Creighton