[Bug 12915] --modify-window should default to 1 for fat filesystems

2020-07-27 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12915 Wayne Davison changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW

Re: [Bug 12915] --modify-window should default to 1 for fat filesystems

2017-07-20 Thread Brian K. White via rsync
Rsync should not be responsible for detecting what a filesystem can handle. That makes the most sense to me. There are countless filesystems, each with their own quirks, and countless mkfs and mount options which just multiplies the possible fs behaviors even more. Best to provide controls

[Bug 12915] --modify-window should default to 1 for fat filesystems

2017-07-19 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12915 --- Comment #8 from Kevin Korb --- The 3602 problem happens when the clocks change not the entire time the clocks are different. If you do a daily rsync then rsync will see 1 hour off timestamps the day after both clock

[Bug 12915] --modify-window should default to 1 for fat filesystems

2017-07-19 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12915 --- Comment #7 from Ian Kelling --- > But here in the US for half of the year you need --modify-window=3602 instead. I think people use vfat because there are a lot of devices out there like android which require it, and they only

[Bug 12915] --modify-window should default to 1 for fat filesystems

2017-07-19 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12915 --- Comment #6 from Ben RUBSON --- Just to clarify, is FAT32 also impacted and requires --modify-window option, or only the old one FAT is ? Thx ! -- You are receiving this mail because: You are the QA Contact for the bug.

[Bug 12915] --modify-window should default to 1 for fat filesystems

2017-07-19 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12915 --- Comment #5 from Kevin Korb --- Actually, I looked it up. It wasn't actually my request I had already dealt with the problem. This is the ticket from the person I was helping:

[Bug 12915] --modify-window should default to 1 for fat filesystems

2017-07-19 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12915 --- Comment #4 from Kevin Korb --- The manual says that with FAT you need --modify-window=2 not 1. But here in the US for half of the year you need --modify-window=3602 instead. The same goes for many other locations. The

[Bug 12915] --modify-window should default to 1 for fat filesystems

2017-07-18 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12915 --- Comment #3 from Brian K. White --- (In reply to Ian Kelling from comment #2) The manuals says useful not helpful. The manual does not say it's good or bad or recommended or any other value judgement. It only describes it's

[Bug 12915] --modify-window should default to 1 for fat filesystems

2017-07-18 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12915 --- Comment #2 from Ian Kelling --- > This would not actually be very helpful. Why? You haven't said. The manual says it's helpful and it's helpful for me. -- You are receiving this mail because: You are the QA Contact for the

[Bug 12915] --modify-window should default to 1 for fat filesystems

2017-07-18 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12915 --- Comment #1 from Kevin Korb --- This would not actually be very helpful. Going between a *nix style timestamp and a FAT one has other issues. Especially if your TZ changes or you are in a TZ where the clock changes twice