Page 2 of 2
Re: _UNPACK_ directories not being removed after 0.7.17 upgr
Posted: May 12th, 2014, 5:04 am
by shypike
No it hasn't been fixed because I cannot reproduce the problem at all.
The next release will contain extra logging to get more diagnostic data.
Only if that brings more info, I can fix it.
Re: _UNPACK_ directories not being removed after 0.7.17 upgr
Posted: May 12th, 2014, 9:22 am
by jt25741
bleomycin wrote:I'm curious if this has been resolved? Disabling folder renaming breaks nzbdrone so that isn't an option for a lot of us. Thanks!
How does disabling folder renaming break nzbdrone? Are there any other side-effects of disabling folder renaming? Looking at it another way, what are the advantages of enabling folder renaming anyways (default)?
I have mine disabled for now..and the unpack folders are not getting left behind any longer. But I am getting some strange behavior I cannot describe too easily yet with Sickbeard. It may or may not be related to making this change. I have not seen a new release to try since the problem originally occurred.
Re: _UNPACK_ directories not being removed after 0.7.17 upgr
Posted: May 13th, 2014, 4:19 am
by shypike
jt25741 wrote:
How does disabling folder renaming break nzbdrone? Are there any other side-effects of disabling folder renaming? Looking at it another way, what are the advantages of enabling folder renaming anyways (default)?
I don't know about NzbDrone, but the concept of having a prefix is meant to help indexing programs.
The idea is that indexing programs should be told to avoid anything starting with"_UNPACK_".
If you're not using such software, then renaming isn't really necessary, except that you won't have a visual indication
of whether a folder contains usable material.
Re: _UNPACK_ directories not being removed after 0.7.17 upgr
Posted: May 13th, 2014, 9:09 am
by jt25741
Thanks shypike for your explanation and help in suggesting a viable workaround for this problem until you can gather more telemetry.
Regards