Question #189893 on LinuxDC++ changed: https://answers.launchpad.net/linuxdcpp/+question/189893
Steven Sheehy posted a new comment: You could manually craft this HashIndex.xml to add the filename, size, timestamp, tth into it (with linuxdcpp not running). You'd have to add a <Hash...> entry and a <File...> entry in the xml for each file. On next startup linuxdcpp will get a list of all files in the shared folders and hash files that are missing. If the file is already hashed, it will confirm that the file size is the same and that the timestamp is newer than the file's last write time before attempting to re-hash it. So if you craft it properly it will do just as you suggested. Or you could just run linuxdcpp on the server (directly or via remote X) and hash it there. Then copy the HashIndex.xml and HashData.dat over to the slower machine when it's done. Either option is probably not ideal for you, but it's workable. Your use case is not exactly very common to warrant such a feature developed since most people don't hash files themselves, have 30TB of data, fast NFS servers, etc. -- You received this question notification because you are a member of LinuxDC++ Contributors, which is an answer contact for LinuxDC++. -- Mailing list: https://launchpad.net/~linuxdcpp-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~linuxdcpp-contributors More help : https://help.launchpad.net/ListHelp
