Hi,
I have to update my observations described in my previous post: now I've seen this happening when running nph-build via telnet, too. So it seems not to be just an environment problem...
I am really wondering why this happens... It occurs randomly. It seems to happen more often when nph-build.cgi is run via cron. What I can't say is if this occurs also when running a build from the web admin, because the script gets a timeout and build staggered is obviously refreshing the pages too fast (there is no "done" message on the last "building category..." message before the page is refreshed and the next category pages are built).
So, does anybody else has a problem like this?
Is it in the code, or is it really a server side problem?
Andreas
http://www.archaeologie-online.de
I have to update my observations described in my previous post: now I've seen this happening when running nph-build via telnet, too. So it seems not to be just an environment problem...
I am really wondering why this happens... It occurs randomly. It seems to happen more often when nph-build.cgi is run via cron. What I can't say is if this occurs also when running a build from the web admin, because the script gets a timeout and build staggered is obviously refreshing the pages too fast (there is no "done" message on the last "building category..." message before the page is refreshed and the next category pages are built).
So, does anybody else has a problem like this?
Is it in the code, or is it really a server side problem?
Andreas
http://www.archaeologie-online.de