Hi!
Maybe can help you:
1. exclude all temporary files/dirs, when rsync'inc like
My sync script: rsync -4aHvP --delete-delay --timeout=90 msync.centos.org::CentOS /var/www/mirrors.neusoft.edu.cn/htdocs/centos/
rsync -4aHvP --exclude='*/.~tmp~' --delete-delay --timeout=90 msync.centos.org::CentOS /var/www/mirrors.neusoft.edu.cn/htdocs/centos/
2. To autoterminate rsync process use "timeout" like: timeout --preserve-status --kill-after=15 7200 rsync -4aHvP --exclude='*/.~tmp~' --delete-delay --timeout=90 msync.centos.org::CentOS /var/www/mirrors.neusoft.edu.cn/htdocs/centos/
here "timeout" send to rsync process SIGTERM signal immediately after 7200 seconds after run. AND also SIGKILL signal after 15 seconds from previous (normal SIGTERM) signal (killing controlled process, if not terminated by signal).
Sure, insert correct _FOR_YOUR_ timers.
3. Maybe, some reason for rsync'ing from nearest/fastest (FOR_YOU) mirror (other China mirror / other Asia mirror)?
Have a nice day!
18.06.20 01:15, sfl@neusoft.edu.cn пише:
Hi Sriram,
I believe, it's must something wrong, either that server or mine, could you help me to identify it?
First, I think the .~tmp~ directory is private, shouldn't in downstream sync list, and Second, in China, the sync speed is very slow (under 100KB/s at most time), and the .~tmp~ has huge size (many GB), will cause too many days to sync, and after, useless.
This issue only happen when I sync from the centosx4 server, I had to terminated it manual each time, or waste days time.
My sync script: rsync -4aHvP --delete-delay --timeout=90 msync.centos.org::CentOS /var/www/mirrors.neusoft.edu.cn/htdocs/centos/
How can I modify it to make it better?
-----Original Message----- From: CentOS-mirror centos-mirror-bounces@centos.org On Behalf Of Prof. P. Sriram Sent: 2020年5月30日 22:57 To: Mailing list for CentOS mirrors. centos-mirror@centos.org Subject: Re: [CentOS-mirror] Dirty file on server
On Sat, 30 May 2020, sfl@neusoft.edu.cn wrote:
This time, is centosx4.centos.org, it has a .~tmp~ directory under 8.1.1911/AppStream/aarch64/os/Packages/, could you check it?
Ahh, isn't this "normal" behaviour, showing that an upstream sync was in progress? Having approriate rsync option (like --delay-updates or something like that) should take care of this, both at centosx4 and the downstream mirror, no?