Page 1 of 1

Speedlimit problem in 0.6.14

Posted: December 11th, 2011, 12:23 pm
by vogelap
Under 0.6.14, I tried to edit my Speedlimit. I keep getting the following warnimg: 2011-12-11 12:10:29,732 WARNING: Unknown action: speedlimit.

Version: 0.6.14
OS: Windows 7, 64-bit
Install-type: Windows Installer
Skin (if applicable): Plush
Firewall Software: None
Are you using IPV6? no
Is the issue reproducible? yes -- edit the Scheduler and add a Speedlimit. Save.

Re: Speedlimit problem in 0.6.14

Posted: December 11th, 2011, 2:08 pm
by shypike
Have you been messing with the ini file?

Re: Speedlimit problem in 0.6.14

Posted: December 12th, 2011, 7:57 am
by vogelap
No... Haven't touched the ini file. SABnzbd was running fine prior to the 0.6.14 update. After I applied the update, I wanted to tweak my Scheduler. That's when the issue showed up.

Re: Speedlimit problem in 0.6.14

Posted: December 12th, 2011, 12:41 pm
by shypike
You're entering a speed limit without the required parameter.
You should enter a value (in KBytes/sec) in the empty box below the selection box.
SABnzbd shouldn't accept "speedlimit" without the parameter, but it does and this will result in a warning at startup.
Just remove the event and re-enter it with a valid numeric value.

Re: Speedlimit problem in 0.6.14

Posted: December 12th, 2011, 4:32 pm
by vogelap
Thanks. I will double-check that all my speedlimit entries have numeric parameters.

Is there some value to indicate "unlimited", or do I just set it to an absurdly high number?

Re: Speedlimit problem in 0.6.14

Posted: December 12th, 2011, 5:03 pm
by shypike
0 equals max speed.

Re: Speedlimit problem in 0.6.14

Posted: December 17th, 2011, 7:44 am
by vogelap
Thank you! It is working as expected now... The problem was that I was trying to set Speedlimit without a number (thinking that doing so would set max speed). I understand now that "0" is the right way to do that.

Thanks.

Re: Speedlimit problem in 0.6.14

Posted: December 17th, 2011, 8:15 am
by shypike
Yes, it's counter-intuitive.
That's why the next release will accept an empty value as "off" and show it like that too.