the multi threaded update script uses 100% cpu usage a lot.
Setup newznab+ on an old computer I had laying around. P4 1.5Ghz with 256MB RAM. Ordered 512MB more of RAM. Everything has been backlogged for just a day and it is still running at 100% CPU pretty much constantly.
Still running great but I noticed nzbs.in was getting some movie releases before I did. Checked where they were finding them and it’s in group alt.binaries.global.quake. I tried adding that group manually since it wasn’t in the list and every time my update script hits it I get: “Could not select group (bad name?): alt.binaries.global.quake”
I can download movies posted to that group (from nzb’s from nzbs.in) so I know my news host has it. This is the only group of the 37 I have indexing that gives this error, and of course it’s the only one I added manually. I saw some people getting this error when they added too many groups so I went through my group list and removed 10 groups that had 0 or just 1 or 2 releases. Still get the same error on the one group. Any ideas? Someone else want to try adding that group and see if it works for them? Seems to get new x264 HD movie releases a couple days before any other group.
I added it… waiting for things to catch up and then I can comment… I did just learn something useful… I’m pretty sure you can back fill your shit extremely quickly… If you log on to irc.synirc.net and “/query newznab !nzbdump YOURNEWZNABID” you get some pretty interesting information… As far as I can tell anyways… just got back from happy hour…