Prevent infinite loop with process dir and keep original files

[terbolous]

Any chance that you could import this pull into this fork?
midgetspy#629

[gitrickm]

Yes please! I just hit this problem this morning.

I have vuze downloading the torrents, then when completed vuze moves the file to the directory that sickbeard monitors. If SB moves the file, vuze gets errors because the file disappears. I thought I'd try telling SB to leave the file there such that I could manually tell vuze to remove it, but then I found the SB was post-processing the files over and over every 10 minutes.

Am I doing this all wrong?

[junalmeida]

Yes, but I prefer to wait this to be merged at least with the development branch of midgetspy, to avoid problems if he decide to use another pull.

[terbolous]

Roger. Any chance of this being merged as well?
midgetspy#686

[lansinghd]

As noted in #149, midgetspy/Sick-Beard@9f309a4 merges this functionality into the development branch and seems to be functional when I manually merged to this torrent fork for testing:

2014-03-25 11:47:04 DEBUG    POSTPROCESSER :: Ignoring file: /path/filename.ext looks like it's been processed already

This creates a native solution to allow the "Scan & Process" and "Keep Original Files" features work together without triggering unnecessary disk i/o and notifications every 10 minutes due to seeding.

I'd love to see this functionality in the torrent fork as I depend on the Transmission RPC client to set a separate path for Sickbeard downloads - which works perfectly, thanks for maintaining this fork!

[junalmeida]

Nice. Going to test this as soon as possible @lansinghd .

[wjbeckett]

Any update on this?
I'm really looking to have this functionality!

[dmarcelino]

+1 This functionality would probably lower the CPU usage on my Synology, where I run SickBeard.

[Mikk36]

+1

It's really annoying to see SickBeard process the downloaded files over and over, because without keeping the original files, you can't share the downloaded files. Isn't this supposed to be the torrent edition of SickBeard?

[rui-castro]

I'm also waiting for this fixed to be merged.
Until that day, I'm using my fork of Sick-Beard (https://github.com/rui-castro/Sick-Beard), that is exactly like this, but has a fix to the "infinite processing loop" applied.

[dmarcelino]

@rui-castro, would you know if your current fork also prevents SickBeard from repeatedly searching for subtitles in cases where it can't find them?
I'm seeing this particularly with anime episodes with odd name patten, where SickBeard is constantly trying to find subtitles driving my Synology's CPU usage.

[rui-castro]

@dmarcelino, besides the patch to prevent the infinite processing loop, my fork is exactly like this one. So, no.

[dmarcelino]

I see, thanks!

[benyjr]

Any up date on this? If I could leave the original files where they are, I wouldn't have so many seeding errors with files being moved all over the place.