![]() Subsequent runs should now be fine.Ĭode: Select all Linux RPi51 4.19.66-v7 #1253 SMP Thu Aug 15 11:49: armv7l GNU/Linux ![]() I doubt there is any "delay", but manually copying the files can easily throw off the timestamps used, in this case by rsync, so not a surprise really that the first rsync run set things correctly. The script might be a bit overkill and complex for the average needs, but I use the same one across multiple systems so I like the generic nature of using system variables IPADD=`/bin/hostname -I | /bin/sed -r s/\ $//g`Įcho "`date` Running script " MODEL=`/bin/cat /sys/firmware/devicetree/base/model` Only difference I see really is that you mount the share, I just connect directly with rsync. Sat Sep 3 00:30: Number of regular files transferred: 28 Sat Sep 3 00:30: Number of files removed: 0 Sat Sep 3 00:30: Number of regular files transferred: 0 Sat Sep 3 00:30: System Type Serial Number I need to investigate further what actually caused the timestamp to "suddenly" be correct.Ĭode: Select all Sat Sep 3 00:30: Running script on IP Address I also ran rsync with the -size-only flag - and maybe this did something with the timestamp. The files were present there, but they were overwritten by rsync. Maybe it was set correctly after running rsync the second time. in the QNAP itself? There were a couple of thousand files and 10GB data, so is it possible that QNAP takes some time updating the timestamps internally? Can there be a delay in setting these by rsync? The rsync process was finished, but can there still be some updatest going on e.g. I saw that suddenly the target files had gotten the correct timestamp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |