I know this isn't really on-topic, but hopefully folks here can help.
I'm sore confused, and I think I'm just missing something I _used_ to
know but can't remember.
A month or so ago I set up rsh to a remote site to do rsync over rsh
(these are internal sites so encryption isn't needed). I'm usi
ok. I've gotten an apache proxy server set up
listening on port 8080. I tried to run the rsync client again thru' the apache
web server. This time, I failed again with the error "bad response from proxy -
HTTP/1.0 403 Forbidden". I looked at apache's access log file and realized that
rsync
I have been trying to get rsync to work through the
proxy server. I am running rsync on a windows 2000 machine. I set the enviroment
variable RSYNC_PROXY to be the proxyhost:proxy port of my company.
Unfortunately, I keep getting the error "bad response from proxy - HTTP/1.0 500
Cache Dete
On Thu, 14 Dec 2000, Mina Nozar wrote:
> Hi. I have just started using rsync and have a problem already.
> Am having a problem already...
>
> Am trying to back up the system disk on linux box A to a disk on linux
> box B.
>
> I run the following script on A:
> ===
> # The name of the ba
Hi. I have just started using rsync and have a problem already.
Am having a problem already...
Am trying to back up the system disk on linux box A to a disk on linux
box B.
I run the following script on A:
===
# The name of the backup machine
BACKUP=B
# List of directories to backup fr
In message <[EMAIL PROTECTED]>, Martin Pool writes:
> I hope this can eventually replace the coding functions in rsync,
> although at the moment Rusty is going ahead on rsync 3.0 with a much
> simpler and less flexible library.
This is the first time I hear of rsync 3.0 -- could you (or Rusty)
c
rproxy development has been moving along. There's a moderately-stable
beta out there, but things have been changing consideraly behind the
scenes.
The main challenge for this year has been to take the existing proxy
and rsync code, and turn it into something that can be reused in
programs like A
