Support Forum

Including the report id in the nzb name is a good idea, so that we can refer back to the report and identify which one it is when there are more than one with the same report title (which happens a LOT, as I'm sure you know  :)  ) Unfortunately the current name of "msgid_XXXX Report Name" ...

When I upgraded from B2 to B4 I had about 60 items in my queue, but had to rebuild it all. Unfortunately I had about 130 nzbs in my backup directory. It took me ages to carefully go through them all and figure out which nzbs should be in the new queue, which ones I had cancelled and which ones had a...

Apologies, but I'm not in a position to be able to test this on B5, but I couldn't see it in the release notes, so it may well still happen. I recently had a par2 repair fail in apparently a rather silly way. The nzb contained 2 separate par sets, one for the main file and one for the sample. SAB ve...

I prefer not to have my nzbs gzipped. Could we have a Config/Switches item to turn this on/off please?

Being able to assign connections to servers based on a configured retention would be a great feature to have. I have 2 servers, one with a fast connection but a short retention, and one with a slow connection but a long retention. I would really like jobs to be passed to the slower one if they are t...

I've now done some more testing with B4 and a cleaned out cache, and it's _much_ better now. I find I have a roughly constant swap usage of ~170MB and ram usage as follows: No items                  18M 1 item in Q and 1 DL  45M 6 items                    82M 8 items                    100M 50 items...

Hi I don't get how you can all be running this successfully on a 32MB machine. I'm finding it eats RAM like popcorn. I started off using B2 and I've now upgraded to B4. I'm using debian sid with Python 2.5.2. With B4 as soon as I run sabnzb.py it takes up 18M ram and 164M of swapfile. With 1 item ad...