Hi there, tunasync [1] is our mirror job scheduler. We do run our mirror job using ftpsync, which is scheduled by tunasync. Besides scheduling, tunasync also collects logs and job status.
As we have to manage a bunch of mirror jobs for different types of mirror protocols, this scheduler, or middleware is essential to us. The output info you got is the returned by the `tunasynctl start debian` command, which signals the backend to start syncing debian with ftpsync. As the tick unit of the scheduler is 5 seconds, the job does not start intermediately. There are also some other conditions that may delay the syncing, such as concurrent job limitation. So don't worry, we do sync debian with ftpsync, and every push is queued and ensured to trigger the syncing. Cheers, Justin [1] https://github.com/tuna/tunasync/ -- Justin Wong On Sun, Jan 29, 2017, at 01:28, Bastian Blank wrote: > On Fri, Jan 27, 2017 at 12:37:03AM +0800, Miao Wang wrote: > > If there should any further questions, please do not hesitate to > > contact us. > > I can connect to both of them. However I neither see the usual ftpsync > reaction on invalid archive names, nor an rsync connection back to the > syncproxy. Instead I get on the ssh connection: > > | /home/tunasync/.config/tunasync/ctl.conf > | [17-01-29 01:25:35][INFO] Use manager address: http://127.0.0.1:14242 > | [17-01-29 01:25:35][INFO] Succesfully send command > > Can you please that ftpsync is actually called? > > Regards, > Bastian > > -- > Every living thing wants to survive. > -- Spock, "The Ultimate Computer", stardate 4731.3 -- 您收到此邮件是因为您订阅了 Google 网上论坛的“THU Opensource Mirror Admin”群组。 要退订此群组并停止接收此群组的电子邮件，请发送电子邮件到[email protected]。 要查看更多选项，请访问 https://groups.google.com/d/optout。
