SABnzbd Forums

The attached Python script clean's up (deletes) SFV files in the job directory, but only if they do not contain a reference to any existing non-NFO file in the job directory. Such files are often leftover after unpacking, and are useless.

Remarks:

• The cleanup is performed only in the provided directory; subdirectories inside it, if any, are not affected.
• References to NFO files in an SFV file are ignored.
• SFV files ending with a number, e.g. "foo.sfv.1", "foo.sfv.2", etc. are processed as well.

If you have a comment for me wrt this script, please consider sending it to me as a PM rather than posting a message here. Just maybe, the functionality of this script can be incorporated as a default option in a future version of SABnzbd+! An alternative but possibly cruder way of handling this might be at the unpack level, such that any SFVs that are present before the unpacking get deleted, but those that were unpacked themselves can stay.

What is wrong with just adding .sfv to the cleanup list of sabnzbd in config>general?

switch wrote: What is wrong with just adding .sfv to the cleanup list of sabnzbd in config>general?

There may at times be an SFV file that contains checksums of extracted files. I don't want a useful file like this to be deleted, which I believe will happen if I add .sfv to the cleanup list.

An alternative but possibly cruder way of handling this might be at the unpack level, such that any SFVs that are present before the unpacking get deleted, but those that were unpacked themselves can stay.

I had a problem with it deleting an SFV file and the PAR2 failing bc of it....

jubei wrote: I had a problem with it deleting an SFV file and the PAR2 failing bc of it....

It can delete the SFV files only after SABnzbd+ has finished with everything else, including par2-based repair and unpacking. This is applicable to R, U, and D modes. What was your Mode for this download set to? Was it set to None? It is inconceivable to me why someone would set the mode to None. Currently, the mode of a download is not passed by the application to the postprocessing script.