Awesome suggestion, but unfortunately it doesn't work in my case. =(
I have noticed, however, that rsync does work from some of the windows servers
to the Debian servers. So even though our main file store can't send files
directly to our Debian servers, I've set up one of the windows servers
I'm not using rsync through ssh since this is on an internal network. Would
pipes still be used?
The only difference I can tell between my situation and Alain's is that my case
the windows client is sending files instead of receiving.
Are there any suggestions for a work-around other than
At 01:26 05.10.2007 -0700, Miles Raymond wrote:
I'm not using rsync through ssh since this is on an internal network. Would
pipes still be used?
The only difference I can tell between my situation and Alain's is that my
case the windows client is sending files instead of receiving.
Are there
We've been using rsync to send updates to our webservers from a central
location for years. All the webservers used to be Windows 2000 Server running
rsync 2.6.3. Recently I've been trying to replace them with Debian servers
with rsync 2.6.9. The central file server is a Windows 2000 Server
On Thu, Oct 04, 2007 at 10:24:23AM -0700, Miles Raymond wrote:
From what I read from google, this seems to be a common problem with
rsync on windows.
Yes, due to a bug in cygwin's pipe code (the pipe that carries data
between rsync and ssh). Until cygwin fixes its pipe code, you can only
On 10/4/07, Wayne Davison [EMAIL PROTECTED] wrote:
Yes, due to a bug in cygwin's pipe code (the pipe that carries data
between rsync and ssh). Until cygwin fixes its pipe code, you can only
reliably rsync data to/from a cygwin system if you avoid pipes (e.g. use
a daemon transfer).
I'm not
