aMule Bug Tracker - aMule | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001817 | aMule | Feature Request | public | 2023-07-15 20:15 | 2023-07-15 20:15 |
| Reporter | guillere | ||||
| Assigned To | |||||
| Priority | low | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Platform | PC | OS | Debian/Linux | OS Version | sid |
| Product Version | 2.3.3 | ||||
| Target Version | Fixed in Version | ||||
| Fixed in Revision | |||||
| Operating System | Any | ||||
| Summary | 0001817: Store ed2k hash usign xattr in the filesystem | ||||
| Description | If shared files are stored in filesystem that support xattr (extended file 0attributes) then store the ed2k hash and a timestamp (of last hash check) using the xattr provided by fs Example: # xattr SharedFile.avi user.ed2k-hash 952edeccce1cf123aeab5813dc344651 user.ed2k-timestamp 2023-07-15.10.20.44 Amule only need to re-hash if modification time of file is grater than user.ed2k-timestamp. | ||||
| Steps To Reproduce | N/A | ||||
| Additional Information | Useful if you need to change shared file/directorys whitout need to rehash all again... in my case a have a "slow" NAS (using nfs4 that support xattr) with a lot of Terabytes of shares and change to another pc and rehash all take forever :-( | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2023-07-15 20:15 | guillere | New Issue | |||
| There are no notes attached to this issue. |