Quote:
Originally Posted by CodeR70
Joe, I know these things can be very annoying, but there are times when you really need the error log. Switching it on when you need it might be too late to really try to track down an issue. Another thing which is a good option is to rotated your logs. This can be based on size or based on a time period. You can also do this with your access log or other log files. In this way you avoid having the logs grow and grow but you still keep the advantage of having them around when you need to. In addition you can have your inactive logs compressed so they don't eat your drive space. All this is a fully automated process. So you or your admins have to set it up once and after that you never have to worry about them anymore. If you notice something in your log file you think is fixable but you dont know how then maybe post some log lines here. If it PHP related or such then maybe I can help. Anyway, just a few thoughts. Feel free to drop me a line private if you prefer.
|
I have it taken care of, I've been a web developer since '94 (C/C++, Perl, PHP, etc). This is however the first time the error log has refused to turn itself off when I needed it to. In the past, I've always left it on so I could debug my code. However, my system (which I coded) is extremely stable and if there is a problem, I'll know how to fix since I code everything long hand.