The strange thing about it is that I had been running the script for
months without knowing it was causing any problem. The hosting
service claims they had warned me about it before, but I cannot
recall any prior communications. I was experiencing much heavier hit
volumes when they decided to make me pull the script (since two of
the major BeOS news sites are down and I am one of the last few
standing until BeNews and BeGroovy come back online.) Perhaps
the higher hit volumes just exacerbated the problem.
> So, this script had been working when tested?
>
> Adding QUIT to the end?
>
> The script as it appears to me, as a regular CGI, shouldn't
> behave that way, so I'd conjecture there's something about
> the SSI method that causing the problem. Wish I could be
> more helpful.
>
> -jeff
