Hi folks, I am hoping someone here can offer some suggestions. Here
is my situation:
I am using rsync over the internet for several hundred clients to
keep them in sync with a master repository of files. The rsync
daemon is listening on port 80, because most of the clients are
behind
On 4/17/07, Robert Denton [EMAIL PROTECTED] wrote:
Hi folks, I am hoping someone here can offer some suggestions. Here
is my situation:
I am using rsync over the internet for several hundred clients to
keep them in sync with a master repository of files. The rsync
daemon is listening on port
Do you mean for example.. Instead of running rsync on port 80, have
rsync listen for requests on 873 as usual, but also have squid
running on the same server listening for port 80 connections, and
then just configure squid to send all port 80 traffic to 873?
Robert
On Apr 17, 2007, at
On 4/17/07, Robert Denton [EMAIL PROTECTED] wrote:
Do you mean for example.. Instead of running rsync on port 80, have
rsync listen for requests on 873 as usual, but also have squid
running on the same server listening for port 80 connections, and
then just configure squid to send all port 80
This is an interesting idea. Here is what I am trying:
I have set up squid to listen on port 81, since rsync on the same
machine is already listening for requests on 80. I have set the
RSYNC_PROXY env var to the hostname:81 and rand a quick test. The
result is that I am getting this
On 4/17/07, Robert Denton [EMAIL PROTECTED] wrote:
This is an interesting idea. Here is what I am trying:
I have set up squid to listen on port 81, since rsync on the same
machine is already listening for requests on 80. I have set the
RSYNC_PROXY env var to the hostname:81 and rand a quick
