Author Topic: default execute command after FULLY complete  (Read 2135 times)

Offline mysteryman

  • Contributor
  • ***
  • Posts: 66
default execute command after FULLY complete
« on: September 03, 2008, 09:01:41 am »
I have a script which runs from altbinz which sorts and organizes my downloads. In most cases this works as expected. However it has been causing problems with some downloads with more than one par files each. In some cases this causes the 'default execute command' to be run 3-4 times!

Idealy, this script should only be run once ALL pars for that collection are done. In many cases there are 3 pars (cd1, cd2, other). The main problem is when cd1 finishes, but there was some recovery done, and by the time cd1 is 'complete' there have been 2-3 files from cd2 finished. My script will move cd1 files to CD1 and cd2 files to CD2... if there is need for parchecks on cd2... those expected files are now unavailable.

Offline cr4zyfr4g

  • Global Moderator
  • *****
  • Posts: 781
  • German n00b
Re: default execute command after FULLY complete
« Reply #1 on: September 03, 2008, 11:04:31 am »
to avoid that: split the collection for each cd and use a different subdirectory for each (you can use the same unrar folder for each so you still have them all in one folder later.

Offline mysteryman

  • Contributor
  • ***
  • Posts: 66
Re: default execute command after FULLY complete
« Reply #2 on: September 03, 2008, 11:47:23 am »
splitting the collection is not always viable if they were already merged into one nzb file when you get them. true, it is still possible, but probably not any better than cleaning up afterward.