v3.6.0Beta1 Orphaned Jobs includes System Folders
Forum rules
Help us help you:
Help us help you:
- 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.
v3.6.0Beta1 Orphaned Jobs includes System Folders
It appears the $RECYCLE.BIN and System Volume Information folders are being counted as Orphaned Job folders.
Re: v3.6.0Beta1 Orphaned Jobs includes System Folders
You can confirm this changed between 3.5.3 and 3.6.0? We didn't change anything about that as far as I know.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: v3.6.0Beta1 Orphaned Jobs includes System Folders
No can do, I'm about to get on a plane.
If it helps...it doesn't count them under normal conditions (otherwise recycle bin and system vol info would always be listed as orphans).
I had 1 real orphaned folder, the list showed 3, the real one, plus recycle bin and system vol info, I then deleted the real orphan and it still showed 2 left, the recycle bin and system vol info. Shutting down SABnzbd and restarting cleared the list. So it appears to only happen if you actually had a real orphaned folder in the first place. Can't say if this is different from 3.5.3 because I haven't had any orphans prior to this.
If it helps...it doesn't count them under normal conditions (otherwise recycle bin and system vol info would always be listed as orphans).
I had 1 real orphaned folder, the list showed 3, the real one, plus recycle bin and system vol info, I then deleted the real orphan and it still showed 2 left, the recycle bin and system vol info. Shutting down SABnzbd and restarting cleared the list. So it appears to only happen if you actually had a real orphaned folder in the first place. Can't say if this is different from 3.5.3 because I haven't had any orphans prior to this.