Hey guys
I'm trying to reduce idle load so that my hibernate works better.
I've come across some funny behaviour in trying to configure
the watched folder.
Keeping the watched folder blank does not seem to stop scans.
If I set the scan time to 0 seconds, suddenly the cpu shoots up to 50%
and stays there.
Is there a 'correct' combination of settings to stop this from happening?
I don't use the watched folder whatsoever, I want it disabled.
thanks for your advice
Watched folder and scan speed behaviour
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: Watched folder and scan speed behaviour
0 is of course the worst possible value.
Don't set it to that value but to 86400 (24 hours).
That it happens is a bug of course, but there's no need to provoke it
Don't set it to that value but to 86400 (24 hours).
That it happens is a bug of course, but there's no need to provoke it
Re: Watched folder and scan speed behaviour
Hey shypike
Thanks for your response. The maximum value of the scan delay seems to be 3600 seconds.
Do you think this could be increased?
thanks
Thanks for your response. The maximum value of the scan delay seems to be 3600 seconds.
Do you think this could be increased?
thanks
Re: Watched folder and scan speed behaviour
Not needed.
As long as you have a blank folder and a non-zero time,
nothing is actually scanned.
The bug is that when you go from a value to zero, it hits an infite loop.
After a restart, that's gone. It's the actual change that triggers the bug.
As long as you have a blank folder and a non-zero time,
nothing is actually scanned.
The bug is that when you go from a value to zero, it hits an infite loop.
After a restart, that's gone. It's the actual change that triggers the bug.