I've just reinstalled and finally got round to installing the multicore version of par2, which from the command line is fine.
However, sabznbd has the "enable multicore par2" box greyed out. I've stuck -t0 in the par2 options section. Should this be enough?
Not quite sure why sabznbd doesn't see it as the multicore version (located in the defaults of /usr/bin/par2 and /usr/bin/X11/par2)
Running Ubuntu 12.04/12.10 with the same effect. Any ideas or should I just ignore it as I've specified it manually?
Cheers
0.71 and multicore par2
Forum rules
Help us help you:
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.
Re: 0.71 and multicore par2
Only for OSX and Windows do we deliver par2 binaries, so there's something to choose.
For Linux, the pre-installed par2 is used.
It's up to you to make sure the multi-core par2 has the name "par2" and will be found
on the $PATH before the single core version.
For Linux, the pre-installed par2 is used.
It's up to you to make sure the multi-core par2 has the name "par2" and will be found
on the $PATH before the single core version.
Re: 0.71 and multicore par2
It has the name par2 and if I run the command par2 with no parameters from the terminal it shows the -t.... as options so the system is seeing it, just not sabnzbd.shypike wrote:Only for OSX and Windows do we deliver par2 binaries, so there's something to choose.
For Linux, the pre-installed par2 is used.
It's up to you to make sure the multi-core par2 has the name "par2" and will be found
on the $PATH before the single core version.
Re: 0.71 and multicore par2
First, did you restart SABnzbd?
Does SABnzbd receive the same $PATH variable as your command prompt?
How is SABnzbd started?
How do you know the new par2 isn't used?
Does SABnzbd receive the same $PATH variable as your command prompt?
How is SABnzbd started?
How do you know the new par2 isn't used?
Re: 0.71 and multicore par2
Yes I restarted SABnzbd
As far as I can tell the $PATH matches what I recieve in SABnzbd
It is an upstart service and has been restarted by sudo service sabnzbdplus restart
I don't know if the multicore version is being taken advantage of, but I would have thought that either the tickbox would be availible once it had detected the multicore version, or if not that someone would be able to tell me that adding the extra parameters to the par2 section would be enough to kick it in to touch.
As far as I can tell the $PATH matches what I recieve in SABnzbd
It is an upstart service and has been restarted by sudo service sabnzbdplus restart
I don't know if the multicore version is being taken advantage of, but I would have thought that either the tickbox would be availible once it had detected the multicore version, or if not that someone would be able to tell me that adding the extra parameters to the par2 section would be enough to kick it in to touch.
Re: 0.71 and multicore par2
download a big broken file - while sab is repairing check top, If its above 1 its likely using more than 1 core
Re: 0.71 and multicore par2
Cheers exussum, didn't think about purposefully looking for a bust file! Will give that a go!
Re: 0.71 and multicore par2
break it yourself if you have to Just remove some lines from the nzb file, the more lines removed the more broke the file is
Re: 0.71 and multicore par2
It cannot work that way because SABnzbd simply doesn't know what's installed.monkey wrote:but I would have thought that either the tickbox would be availible once it had detected the multicore version
Given the extreme range of Unix/Linux/WhateverPosix systems,
we just assume the simplest situation: that the user or the package creator has done the necessary steps.
This is true for par2, unrar and unzip.