Unpacking Details

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
SABTerry1990
Newbie
Newbie
Posts: 3
Joined: June 9th, 2017, 10:43 am

Unpacking Details

Post by SABTerry1990 » July 10th, 2018, 3:42 pm

When something has finished downloading, an unpack process starts at some point.

My Temporary Download folder is on an SSD drive. I was hoping the unpacking would also occur on the SSD drive and then when the unpack is finished, the unpacked files would be moved to the Completed Download folder on a spinning HDD. I'm running this in Linux on a low-powered Banana Pi and think the unpacking would be more CPU/hard disk intensive than the copy from the SSD to the spinning HDD. That's why I'd prefer to have the unpacking done on the SSD.

In a recent download, I noticed that the unpack was occurring in the Completed Download folder. Is that what's supposed to happen?

FYI, I use nzbToMedia as a post-processing script. The SABNZBD log looks like SABNZBD is doing the unpacking and then calls the script.

FYI, I'm still running 2.1 but I'm in no rush to upgrade as everything is working well. I will upgrade if the newer versions changed this behaviour or have configuration options to change the behaviour.

User avatar
sander
Release Testers
Release Testers
Posts: 6351
Joined: January 22nd, 2008, 2:22 pm

Re: Unpacking Details

Post by sander » July 11th, 2018, 7:06 am

I believe it's correct how you describe it.

Maybe this works: set Complete also to your SSD, and run a post-process-script to move to your HDD. Or in your case: alter nzbToMedia to do that.

HTH

SABTerry1990
Newbie
Newbie
Posts: 3
Joined: June 9th, 2017, 10:43 am

Re: Unpacking Details

Post by SABTerry1990 » July 11th, 2018, 11:11 am

I was looking through the code and saw that the temporary working directory is set to the same value as the working directory which eventually is the completed directory.

In any case, your suggestion is great. I have nzbToMedia already set to move the file once it's completed.

So, your suggestion to move Complete to my SSD is also a great suggestion. Works out to do exactly what I need and no changes needed. I hadn't thought of that.

Thanks!

User avatar
safihre
Administrator
Administrator
Posts: 2645
Joined: April 30th, 2015, 7:35 am
Location: Switzerland
Contact:

Re: Unpacking Details

Post by safihre » July 11th, 2018, 3:27 pm

And then also update to 2.3.4 ;)

Maybe Direct Unpack is also having an effect?

SABTerry1990
Newbie
Newbie
Posts: 3
Joined: June 9th, 2017, 10:43 am

Re: Unpacking Details

Post by SABTerry1990 » July 11th, 2018, 11:07 pm

Will be updating to 2.3.4 soon :)

Where can I find more info on Direct Unpack?

User avatar
safihre
Administrator
Administrator
Posts: 2645
Joined: April 30th, 2015, 7:35 am
Location: Switzerland
Contact:

Re: Unpacking Details

Post by safihre » July 14th, 2018, 3:13 am

Direct Unpack starts the unacking to the Complete Folder while the download is still active, so you might already see files appear there while it downloads still.

Post Reply