Add TODO section to README.
Chris Pressey authored 4 years ago
GitHub committed 4 years ago
153 | 153 | |
154 | 154 | (or whatever.) |
155 | 155 | |
156 | Notes | |
157 | ----- | |
156 | TODO | |
157 | ---- | |
158 | 158 | |
159 | If `rsync` encounters an error, it will abort, having only partially completed. | |
160 | In particular, if it encounters a directory which it cannot read, because it | |
161 | is for example owned by another user and not world-readable, it will abort. | |
162 | `ellsync` does not currently detect this properly (if it is detectable (I hope | |
163 | that it is!)) | |
159 | * If `rsync` encounters an error, it will abort, having only partially completed. | |
160 | In particular, if it encounters a directory which it cannot read, because it | |
161 | is for example owned by another user and not world-readable, it will abort. | |
162 | `ellsync` does not currently detect this properly. It should be made to handle | |
163 | it gracefully, if possible. | |
164 | * On external media, a file may become corrupted; `rsync` will not detect this | |
165 | by default. My theory is that this is because the timestamp matches, so it | |
166 | doesn't check the contents. See if there is an option to `rsync` to ignore | |
167 | the timestamp, or otherwise work around the timestamp issue. One option might | |
168 | be to run `diff` on every pair of files, and invalidate the timestamp on any | |
169 | files that do differ. | |
170 | * On external media on my OS, sometimes the sync is very fast, but the subsequent | |
171 | unmount/"writing data to device, do not remove" phase takes a very long time. | |
172 | See if there is a way to call `fsync` on the files updated by `rsync` so that | |
173 | the delay happens at sync time. | |
174 | * Tab-completion of stream names. | |
175 | * (Aspirational) Ability to convert the backup router to a `dot` file (`graphviz`) | |
176 | so that the relationships between the streams can be easily visualized. | |
164 | 177 | |
165 | 178 | History |
166 | 179 | ------- |