Timeline for Why does rsync fail to copy files from /sys in Linux?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 25, 2013 at 18:56 | history | edited | mattdm | CC BY-SA 3.0 |
typo
|
| Apr 25, 2013 at 12:31 | vote | accept | Eugene Yarmash | ||
| Apr 24, 2013 at 19:19 | comment | added | goldilocks | I'd presume they have this behaviour because until you actually read them, what's "there" is not absolutely certain; the read is really a request for dynamic information from the kernel. So the kernel does not try to give accurate details WRT to the file size, etc, in advance, and as you point out, rsync takes such a discrepancy as a bad sign. | |
| Apr 24, 2013 at 18:55 | history | edited | mattdm | CC BY-SA 3.0 |
added 153 characters in body
|
| Apr 24, 2013 at 18:32 | comment | added | mattdm | Sorry, I wasn't clear. Rsync specifically checks for files truncated during read and throws this error. | |
| Apr 24, 2013 at 18:29 | comment | added | Bratchley | Pfft, where's the fun in not figuring out why rsync in particular fails? | |
| Apr 24, 2013 at 18:20 | history | answered | mattdm | CC BY-SA 3.0 |