It appears the script assumes an rsync daemon listening on TCP port 873.  Carl, is there some reason to not use ssh instead?  Rsync can support this trivially with much improved security properties.

— jb
On Mar 10, 2025 at 18:45 -0400, David Cooper <david.cooper@genworks.com>, wrote:

common-lisp.net is now pointing to the same IP addresses as gitlab.common-lisp.net (which is the same as future.common-lisp.net). 

What is that rsync URL protocol? Is that a service we need to set up on the new host? 

If so, Carl, would you consider setting that up for us if I provide credentials?

Dave Cooper



---- On Mon, 10 Mar 2025 17:37:36 -0400 Carl Shapiro <cshapiro@panix.com> wrote ---

Dear common-lisp.net administrators,

We had been relying on rsync to transfer artifacts for the cmucl.org
website from common-lisp.net. The script, which did this periodically

rsync -aqvz rsync://common-lisp.net/project/cmucl/downloads/ .

now times out. I tried referencing the host gitlab.common-lisp.net but
that seems to have no effect. Is there a new host I should?

Kindly,

Carl