Rsync saves file as .fileName.randomStr while in transfer then renames it. That way the transfer is atomic.
What you might see might be file disappearing on remote side, permission or diskspace issues on local side. I'd check for something like that. Tomas On Mon, Nov 25, 2019, 11:32 Rich Shepard <[email protected]> wrote: > On Wed, 6 Nov 2019, Galen Seitz wrote: > > > rsync -havP --no-o --no-g --safe-links --timeout=60 --contimeout=30 > rsync://slackware.cs.utah.edu/slackware/slackware64-14.2/ > /my_mirror/slackware64-14.2/ > > Galen, > > The Utah site is not a current mirror. Using the above syntax: > > $ rsync -havP --no-o --no-g --safe-links --timeout=60 --contimeout=30 > rsync:// > mirror.slackbuilds.org/slackware/slackware64-14.2/patches/packages/ > /opt/Slackware/slackware64-14.2/patches/packages/ > > produces this error on each file: > > rsync: mkstemp > "/opt/Slackware/slackware64-14.2/patches/packages/.bind-9.11.13-x86_64-1_slack14.2.txt.UAbg1O" > failed: Permission denied (13) > 336 100% 0.49kB/s 0:00:00 (xfr#7, to-chk=411/419) > > I don't understand 'mkstemp' or why the packages are supposed to be written > as hissen files (initial '.' on the filename) so I'm not seeing my error. > > Regards, > > Rich > > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
