Ok,
You can sort of fudge things if you can build via telnet.
&build_update_counters();
&build_update_newpop();
&build_stats();
&build_detailed_view();
&build_home_page();
&build_new_page();
&build_cool_page();
&build_rate_page();
&build_category_pages();If you've run an aborted build, where you at least started the category
pages, you can put a # in front of each of the subroutines above, and try running _just_ the &build_category_pages()
next time you run the nph-build, don't forget to uncomment (doing right after you run this is a good idea) the lines above, since if you don't &build_stats() you wont update anything, and you won't build properly.
None of the routines are dependent upon one another, but should be built in order. You can save some time, maybe squeeze out a few more categories by doing that.
But, if you are timing out, see if you can get additional CPU time from your ISP, or one of the other suggestions posted here.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
You can sort of fudge things if you can build via telnet.
Code:
&build_backup(); &build_update_counters();
&build_update_newpop();
&build_stats();
&build_detailed_view();
&build_home_page();
&build_new_page();
&build_cool_page();
&build_rate_page();
&build_category_pages();
pages, you can put a # in front of each of the subroutines above, and try running _just_ the &build_category_pages()
next time you run the nph-build, don't forget to uncomment (doing right after you run this is a good idea) the lines above, since if you don't &build_stats() you wont update anything, and you won't build properly.
None of the routines are dependent upon one another, but should be built in order. You can save some time, maybe squeeze out a few more categories by doing that.
But, if you are timing out, see if you can get additional CPU time from your ISP, or one of the other suggestions posted here.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
