Page 1 of 1

[Solved] Treating incomplete files as finished or making them available

Posted: November 23rd, 2010, 5:24 am
by mind_the_gap
Hi,

for my usenet connectivity I use Sixxs. So it hazzens from time to time (for older posts) that I can't get the full collection of files, but that some files missing some parts. Normally this is a retention issue from the server and I have no way of getting the missing bytes.

Two years ago I was still using Windows and used to use NewsLeecher. Files that were not complete and but had no chance of getting done were just copied to the output folder, but with the file name in capital letters. This made it easy for me to use QuickPar (even with incomplete Par2 files) on the collection. Most of the time I got it repaired.

In sabnzbd however I can't seem to get a workflow like this. Every time a file does not finish, sabnzbd waits and hopes it gets the missing parts somewhere in the future. Is there a way I can get the incomplete files to the incomplete folder, maybe renamed in a verbose way (like capital lettern, or an extra extension)? Because if I could, I would be able to continue repairing downloads like with NewsLeecher.

Here is some info on my setup:

Version: 0.5.5RC2
OS: Ubuntu 10.04
Install-type: linux repository
Skin (if applicable): Default
Firewall Software: None
Are you using IPV6? yes
Is the issue reproducible? yes

Cheers,
Tom

Re: Treating incomplete files as finished or making them available

Posted: November 23rd, 2010, 12:01 pm
by inpheaux
As we discussed at great length on IRC, what you're asking for is either already being done (SABnzbd puts incomplete files in the incomplete dir, moves them to the _FAILED_ dir if it fails) or pointless (constructing a rar on the fly rather than constructing it once we've downloaded all the articles wouldn't really help anything).

Re: [Solved] Treating incomplete files as finished or making them available

Posted: November 23rd, 2010, 12:20 pm
by mind_the_gap
Indeed, my issue is solved now. Different problems came together here. I did't know that sab does try to get everything from eveywhere and then tries to repair. Now my problem is that I use unreliable serlers and this way some nzb's may stay a long time in the queue. By setting these servers to "optional" the articles were finished even if not completed. Sometimes -- like in my case -- this blocks the repairing.

Anyway, Thanks for the help.