.nfo file preview / nzb pre-processsing script ?

[eldon]

Hi,

I'm a long time nzbget user, i'm mostly satisfied with it but been frustrated with a couple of things so i decided to take a look around. Sabnzbd looks very nice but there are a couple of things that aren't there, or maybe i missed them ?

I'm using my nzb daemon on linux with the web frontend.

I was wondering if there's any way to "force" a file download when a nzb is queued, based on filename extension (.nfo).

Let me explain a bit, the first thing i did after using nzbget was to take advantage of its nzb pre-processing script, which is supposed to process the nzb before it is added to the queue. I didn't use that to modify anything in the nzb file but i use it to fetch the nzb's .nfo file from the news server so it can be made available in the web interface. i had to customize the default web interface a bit but it's not too much work usually.

The nfo is fetched by a perl script independently from the regular daemon queue. The web interface then looks for a file based on the queue id and then makes it available to the user.
I also use the nfo to parse some external links, imdb especially, so they can be accessed easily from the frontend queue as well.

As far as i can see there's no mention of nzb pre-processing script in sabnzbd, would there be any way to script/process the newly added nzb ? or for that matter dowload the .nfo file when an added nzb has one ?

thx

[shypike]

There will be a pre-queue script in the next major release.
First Beta within a month.

[eldon]

okay so i take it at the moment there's no way to launch a script when a nzb is added.

Is that beta already available on some svn repo ?

One more thing if you're working on new features, there's another thing i've been working on nzbget but was more complicated to do from outside scripts, which is to take into consideration the age of the files.
The age can be fetched from the headers of parts on the server but i also found out that some (if not all?) nzb indexers provide the "date=" parameter for each node, making it quite easy to know the age of the oldest file of the collection thus the age of the collection.

The age info is also quite important imho, we all know that usenet storage has an expiration date and my nzb daemon should know about that and take appropriate actions when the expiry date, known from a config entry, is about to be reached, meaning it would start the download on its own even if the collection was paused, which is always the case for me.

i wasn't able to do that on nzbget for nothing is triggered on a regular basis, it could be a cleanup/update script called every x minutes, and had to implement a daemon sidekick running on its own and using the api to check dates and start collections, but that's quite ugly.

Anyways thx for your answer, i'll wait for the next beta if it's not available at the moment.

[shypike]

We will do something with the job age at sometime.
Currently you can already have the queue sorted "oldest first".