> On 20. May 2020, at 17.51, Felipe Gasper <fel...@felipegasper.com> wrote: > >> >> On May 20, 2020, at 10:46 AM, Sami Ketola <sami.ket...@dovecot.fi> wrote: >> >>> On 16. May 2020, at 3.46, Felipe Gasper <fel...@felipegasper.com> wrote: >>> >>> 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! >> >> >> Is there any reason why you are doing it this way and not using it the way >> it is usually used? backup does not support -1 btw. >> >> doveadm backup -u john -R ssh sshuser@remote "sudo /usr/bin/doveadm >> dsync-server -u john" > > Isn’t this actually the same syntax that I’m asking about, where > <destination> is a command name and arguments? I guess the documentation is > just in want of emendation to mention this usage?
Basically yes as long as the command takes doveadm protocol as input and output. Sami
