search for: headsprout

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 firewalls that only allow outbound port 80 (and other common ports). This works fine for most of them

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 that this is the logical next step for rsync and is the one feature I most desparately need. What

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, but the directories themselves will be listed as needing updated. It would be nice if I could

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 -------------- next part -------------- HTML attachment scrubbed and removed