There've been some repairs lately, with a lot of overnight downtime. This mark-command is of course available via api too. If user decides the download is OK he can mark item as good and then all other duplicates are deleted. It may have bad video quality or wrong audio etc. After successful download nzbget doesn't delete other (failed or waiting) duplicates because there is a chance the succeeded one isn't good enough. Term duplicate in regard to nzbget means the same title (same movie or same episode), it can be the same video file but can also be a different one with different quality. If you have HealthCheck=park and ParScan=dupe you don't need HealthCheck=none. What if I want to use HealthCheck=None for certain manually-added duplicates. Just like you could set KeepHistory to 365 if you would have spare 12TB you can set it to 5 too, right? :)įor older stuff most failed downloads are missing completely and therefore don't consume space. In 30 days (and this applies to a rolling average too), nzbget will accumulate 1TB If you automate the first download usually succeeds. On average, there'll be about 5 downloads before success. If the par recovery fails, delete all the duplicate entries from disk" I would also like a way to let NZBGet know "Don't expect any additional duplicates. Fine-grained control could help curb ballooning disk usage. I think it might be useful to allow a per-download HealthCheck, and expose it via the web interface (when adding files) and rpc (scripts/automation). No automation-app supports duplicates and duplicate par2 recovery. Unfortunately, it is too early to determine which HealthCheck setting I should use. Once all duplicate entries have been downloaded and par recovery has run, it would be convenient for NZBGet to automatically delete the input files. So manual downloads shouldn't expect newer duplicate entries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |