[lierduh]

Originally Posted by Imhotep

oh buggar! now I have an even bigger problem. This is from my host...



:ermm:

Is there any way to make this script less system intensive?

I run each 10 minutes. It takes a few seconds to run each time. If you were using the old script and run every 5 minutes. Then if the script is called before the first one is finished. You can push the server over the edge! The new script prevents this. The new script is less system intensive.

Depending on how many messages stored on the server, the first time the script runs, it can take a long time to import all the messages. You should be able to set the last message number to a high one. That way you ignore all the older messages, only import the new ones. To find out the current message number, open the news post using a normal browser, look for Xref in the headers.

Xref: freenews.iinet.net.au aus.tv.pay:132041

The 132041 is the message number.

Check your current message setting in the nntp_groups table against what is on the server, and set the lastmsg for that group to the latest message number. Run the script manually, keep an eye on the server load. If you have shell access, type "top" should show. After you are sure that your script is not a resource hog, email the support nicely and explain to them you have fixed the problem.

(The next version will be even less server intensive.)