On 7/11/25 11:00 AM, Joe Average wrote:
Robert Moskowitz wrote:
...
But is there some way to evaluate the source and see if any changes have
occurred since the last rsync (or some time) and only trigger rsync
accordingly?
filtering/investigating the output of rsync's "--dry-run" option ?
The whole point is to reduce rsync activity. Dry run is a complete
compare of the source and destination.
It may just be a mental exercise and not worth it. Every night I have
an rsync job that downloads the latest Internet Drafts. There is
currently 168694 files in my download directory. So every night rsync
is comparing that to what is in the IETF repo with:
rsync -tvz rsync.ietf.org::id-archive/*.txt /home/common/ietf/drafts
So what am I concerned about backing up a dir tree with a couple
thousand files?
Learning....
:)
And why do I maintain a complete copy of all IDs? At least the txt
ver? Because! And I have needed them on flights to whereever.
Also have all RFCs. On a call today, I had to bring up two to look at.
Much faster than going to datatracker.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
