[geeklog-devel] 1.5 error.log when DB dies

[Dirk Haun]

Tony Bibbs wrote:


>so it write error.log in the directory of the script that first

>encounters the MySQL error.


I know, I've already "fixed" that in CVS - it catches this case (and a
few related ones) and simply doesn't log at all then. Not ideal, but
better than leaving stray error.log files all over the place.



>(this assumes your webserver

>could even write there in the first place which is probably a bad

>thing...


... and which, of course, would throw _another_ error, hiding the
original error.

bye, Dirk


-- 
http://www.haun-online.de/accu/