Hello, Some code that I didn’t write but am maintaining passes a local script’s path as dsync’s “destination” argument, like so:
dsync -D -u john -v backup -R -1 "/code/dsync_client.pl" 127.0.0.1 j...@mydomain.org dsync_client.pl establishes a TCP connection with a remote dsync process then acts as a proxy between the two dsync processes. “127.0.0.1” and “j...@mydomain.org” are given as arguments to dsync_client.pl. I don’t see this usage described in dsync’s man page. I just want to be sure: is this a supported use of dsync? Thank you! cheers, -Felipe Gasper