rsync on multiple ports?

Hi all, I need my rsync to listen on port 8090 as well as on the standard rsync port. Is this possible, and if so, how does one do this? Thanks! Robert -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read:

Re: http as a transport for rsync?

On May 3, 2007, at 8:58 AM, Bob Bagwill wrote: On Wed, 02 May 2007 12:33:38 -0400, Robert Denton [EMAIL PROTECTED] wrote: Given the increasing reliance on proxies and filtering devices, it is harder and harder to rsync across the net. Do you think we will ever be able to use http

http as a transport for rsync?

Given the increasing reliance on proxies and filtering devices, it is harder and harder to rsync across the net. Do you think we will ever be able to use http as a transport for rsync? For example, when will I be able to do this: rsync -arv http://rsync.domain.tld/webroot It would seem

Exclude dirs but not files??

Hi all, is it possible to exclude directories without excluding the files _in_ the directories? I ask because one of the things I do on a nightly basis is do a recursive dry-run against an entire webroot with the size-only option. Very often, all the files themselves will be just fine,

Re: Exclude dirs but not files??

This works in conjunction with the --size-only option as well. Thanks! Robert On Apr 30, 2007, at 2:14 PM, Wayne Davison wrote: On Mon, Apr 30, 2007 at 12:14:41PM -0400, Robert Denton wrote: Very often, all the files themselves will be just fine, but the directories themselves

Re: Rsync for hp 3000

Good luck getting IIRC to compile. If I recall correctly, it is nearly impossible. ;) Robert On Apr 25, 2007, at 2:22 PM, William Wang wrote: Chris, Thanks for your input. I will definitely look into IIRC. Our requirement is very simple (at same time it's hard). We don't need SSL or

HTTP encapsulated rsync??

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

Re: HTTP encapsulated rsync??

:27 PM, Aaron W Morris wrote: 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

Re: HTTP encapsulated rsync??

Morris wrote: 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