New To Rhash, having multiple issues (it's probably me)

[is42theanswer]

Just want to start by saying that Rhash is a wonderful tool and all the speed optimizations you've made to it really make it so much faster than anything I've ever used, so thank you for that. My problem really is that I'm brand new to the program and while the standard documentation of switches is there, I'm having some trouble making them work together. I don't know if there's a website out there with some good examples of all this that I just haven't found, but if there is, I'd appreciate if someone could post the link. For the record, I'm using Rhash 1.4.4 on Debian.

As an example, I'd like to script either traversing directories that may or may not have sfv files in them and if there is a sfv file, then it would verify the checksums against the file in that directory. I know there is --file-list= and it sounds like you can put one directory on one line to check, but what is happening is if I run rhash from /home using rhash -c -C --speed -i /home/A/*.sfv, and the sfv files are in /home/A, /home/B, and /home/C, it will find the sfv file but won't find the files to verify. Only if I run rhash -c -C --speed -i *.sfv in the same directory as the files that are in the sfv does it find them. Can it check for a sfv file in each directory and know that the files to be verified are in that same directory?

Next, when it comes to creating sfv files, I'm having several problems. I used rhash -ufoo.sfv -C -i --speed --exclude=.sfv,.md5,.sha1,.par,.bad,.missing,.nfo,.jpg,.txt /home/A/foo.*. Again, if I run this outside of the directory of the file I'm creating a sfv file for, it creates this file in THAT directory (/home), not the directory where the files it just hashed are (/home/A). In the sfv file itself when done this way, it created a comment in the sfv, along with the tagline of the program a comment on each line of each file with the /absolutely/longest/path/possible along with the file size, and then includes the path with the CRC32 value. When I run this in the directory where the files are, it creates just the lines with the CRC32 value, but no path, and no comment at all. I'd like there to be a comment that has the file size of each file but WITHOUT the path, just the filename. Is that possible?

The next problem is, it is processing files that I thought I'd excluded. I found an example for crc-accept, and I used the same format (no spaces between the command and the period), but it's not working.

Finally, what would really be great, is if the sfv could be auto-named based on the filename. As a result of the exclusions, all the remaining files to be hashed in a given directory have the same name, just different extensions. If the name of the file was genericfile2023.zip, then it'd be great if the sfv file would be named genericfile2023.sfv. In the output format options, it seems like %f might be able to help me here but I'm not sure how to implement it. And if I could have it make a separate sfv file for each directory, that'd be perfect.

I appreciate any and all help.

[is42theanswer]

So, I've been trying to get the exclusions to work a little bit more and no joy. I've tried --exclude=.sfv,.txt,.jpg - both after --speed and at the end of the line (after everything else), and --exclude .sfv,.txt,.jpg (in the same two places in the command), it still processes hashes for the excluded files. I've also tried the same thing in Windows; same result.

In the process, I've also tried the opposite, e.g., to use --accept. Same variations as above, and also, same result. I even tried adding it to "rhashrc" in both Linux and Windows, and again, it didn't stop it from hashing the files I excluded (when I tried it that way), or that I accepted (when I tried it the other way). I just don't know what I'm doing wrong. The only thing I can think of; when I type rhash -h, the list of options DON'T include either --accept or --exclude. Could that be the problem? That these options are no longer in the program?

One small victory: I did manage to figure out how to use --printf to get the formatting of the sfv to output what I want.