SABnzbd seems to make fully downloaded files "busy"

[jkinghome]

Part of my workflow is to use Hazel to move completed downloads to an external network. Many times my workflow can't be completed because the downloaded files are still marked being used by SABnzbd, even restarting will not work. The only thing that releases them is by uninstalling SABnzbd and reinstalling.

Any ideas on what the problem is?

Thanks!

[shypike]

Does Hazel run as a user script?

[jkinghome]

To be honest, I am not sure what the app uses to do it's stuff. Sorry

[jkinghome]

I worked out what the problem is. When files are downloaded, then unRAR'ed, the timestamp of the unRAR'ed file seems to be set to some in the future, sometimes 40-45 mins, or even 2 hours ahead. Hazel thinks that is is still being used - when I change my clock, Hazel fires it's folder rules.

Question is, why does my timestamp on the unRARed files reflect a time in the future, rather than taking it from the actual time??? Ideas?

[shypike]

Could be a timezone problem, either at your end or at the uploader's.
Does it also happen for jobs that are weeks old (i.e. uploaded weeks ago)?

[jkinghome]

I originally thought that, but 1) the timestamp doesn't match any timezone 2) my time zone is correct and 2) it happens with nzbs that are posted <1hr or many days/weeks/months old