SABnzbd Forums

Sometimes when unparring very large files, I'd like to pause the process while watching a movie, etc.  Is there any way to do this? It even seems that when quitting sabnzdb, it won't quit till the process is done.

Thanks!

Pausing is technically impossible, so we cannot offer that option.
So far the only thing you can do is kill the par2 or unrar process.
It will mean a failed download, although with 0.6.0 you can retry post processing.

So I can kill the process running in osx and it won't delete the files? Where do I retry the post processing?

thanks!

shypike wrote: Pausing is technically impossible, so we cannot offer that option.
So far the only thing you can do is kill the par2 or unrar process.
It will mean a failed download, although with 0.6.0 you can retry post processing.

No files will be deleted.
Failed jobs will have a retry link/button in the History view.
You may have to pause downloading too
because when you stop par2, it may start downloading extra par2 files
and have another go with the par2 program.

An alternative would be to switch post-processing on and off in the scheduler.
So no post-processing during prime time.

shypike wrote:
An alternative would be to switch post-processing on and off in the scheduler.
So no post-processing during prime time.

Even tho you can set the schedule, I don't believe this is actually working.  I have a schedule set to pause and resume and it still carries on throughout the hours specified.

Looking through the source, I think the "scheduler.py" is not setting the correct paused variable.

In "scheduler.py", i see PostProcessor.do.pause = pause_post in a couple places to set the paused status of the post processor, but in "postproc.py", I don't see a pause variable, only a paused. As initilized by self.paused on line 76.

I only looked at this quickly (current revision branch 2775), so I may have missed something, but from first glance, it seems like the wrong variable is being set for this type of schedule.

A pro-active user!
You are absolutely right, the code is wrong.
Probably introduced by a recent refactoring action, because it worked before.
That's dynamic languages for you: formally the code isn't even incorrect.

Will be fixed in the next Beta.
In the mean time you can just replace 'PostProcessor.do.pause' by 'PostProcessor.do.paused' in scheduler.py

Thanks.

Cool! Glad you were able to find another bug, even if I wasn't able to create it directly. :-)

Will try the next beta.

-- Joshua

Ok, so I did as discussed and killed the UNRAR process from the Activity Monitor on OS X... however...the jobs are marked as completed and not failed. This is also on the 6.0RC1... any idea why these wouldn't be marked as failed?

Probably because Windows OSX doesn't give a return code that indicates trouble.
I would need to check this further.
BTW: did you turn off the "unpack_check" option (see here: http://wiki.sabnzbd.org/configure-special )?

Definitely didn't change the default unpack_check option.

Let me know how else I can be helpful.

shypike wrote: Probably because Windows doesn't give a return code that indicates trouble.
I would need to check this further.
BTW: did you turn off the "unpack_check" option (see here: http://wiki.sabnzbd.org/configure-special )?