Disclaimer: I searched both the forum as well as launchpad for dupe feature request and didn't see this specific feature requested. The info on launchpad also looked somewhat dated.
I'm curious if there's anyway to add a switch to enable finished jobs to be sent to the Recycle Bin, or jobs that have errors not to be deleted? I'm encountering an increasing number of downloads that are either perceived as incomplete by sabnzbd and promptly deleted, or the PAR files are includes in separate NZBs which sabnzbd cannot, understandably, access. There are occasions when these incomplete jobs can be repaired by PARs included in separate NZBs, but the files have already been deleted.
I won't pretend to know it all and look to the devs for any suggestions that might not require additional code?
It's just a shame to download some large (10+ GB) files that could have easily been repaired had the RAR files not been deleted.
Thanks to the devs for continuing to make sabnzbd an indispensable tool for accessing USENET.
Request for Recycle Bin support for sabnzbd Windows
Re: Request for Recycle Bin support for sabnzbd Windows
If you think that SABnzbd fouls up verification, then disable the "Enable Par cleanup" option in Config->Switches.
BTW: SABnzbd doesn't delete the files of jobs it thinks are failed.
BTW: SABnzbd doesn't delete the files of jobs it thinks are failed.
Re: Request for Recycle Bin support for sabnzbd Windows
As a workaround, I've simply selected +UNPACK as default and delete the files manually.shypike wrote:If you think that SABnzbd fouls up verification, then disable the "Enable Par cleanup" option in Config->Switches.
BTW: SABnzbd doesn't delete the files of jobs it thinks are failed.
This issue might occur in only 1 of 10 downloads, so it's not affecting every job. And with the new practice of randomizing file names, the PAR feature is required for automated extraction. I have noticed some unexpected behavior with the PAR feature in sabnzbd, though.
For example, shortly after posting this comment, I found a folder in my completed downloads directory with the UNPACK prefix added to the folder name? Even though the sabnzbd GUI showed that repair/extraction had failed, the extracted files were present and complete, along with two presumably repaired RAR files?
I've noticed the UNPACK folders in the sabnzbd working directory, but never in the completed downloads directory, which is actually an SMB share mapped to a drive letter shared from a NAS. I haven't changed my folder paths since initial setup, so I'm not quite sure where this behavior is coming from.
Please share any thoughts you have. I'm open to trying any diagnostics to determine what's going on here.
Thanks!
Re: Request for Recycle Bin support for sabnzbd Windows
Do you have some sample NZB files that illustrate this behaviour?
Please email to [email protected] and add the URL of this message.
Please email to [email protected] and add the URL of this message.