On Mon, 2003-10-06 at 15:00, Krištof Petr wrote: > Daniel J McDonald wrote: > > >On Mon, 2003-10-06 at 07:42, Krištof Petr wrote: > > > > > >>Lionel Bouton wrote: > >> > >> > >> > >>>The problem is that on the servers' side (main site and mirrors) > >>>you'll have to set up rsync servers instead of http servers. As a > >>>mirror admin this won't be good news for me... > >>> > >>> > >>> > >>rsync server setup isnt hard. Simple example looks like: > >> > >># rsync server config > >># > >>use chroot = no > >> > >> > >[...] > > > >But this is only the beginning. You also have to set up new firewall > >rules - probably on the box itself and on the front-end firewall > >protecting the box. And you might have to add load-balancer rules. And > >if you have virtual domains set up, it can become even more complex. > > > >Then, the clients have to open their firewalls for yet another port.... > > > > > > rsync server can run on port 80. Clients can use standard http proxy, so > you need no additional setting. > > Petr
Does rsync support http redirect codes ? If there are several servers and I want to redirect requests to the "nearest" or "least used" server. Yes rsync is great for many things, but it's not a miracle cure for every IT problem. In theory, one could extend freshclam to support rsync as a transfer method for updates, but a separate mirror system would have to be set up. Some mirrors could provide both update methods, some just one... but is the extra trouble worth it ? I've worked for companies where setting up a new http virtual servers is easy, but getting management to approve installing a new "service" like rsync takes more time. Regards, Miguel Dias
signature.asc
Description: This is a digitally signed message part
