New Log Level

[Tony]

I think maybe should add a new log level that has what you'd expect on other web server while not including other things you wouldn't expect. Right now to get the sort of Apache logs you'd want on shared hosting you need to set it to INFO level. So in order to get this:

2010-04-13 13:24:56.183 [INFO] [1.2.3.4:58717-0#APVH_domain.com] File not found [/home/username/public_html/domain.com/robots.txt]

You also have to take on this portion of the info notices:

2010-04-13 13:24:57.104 [INFO] Remove pid: 29566
2010-04-13 13:24:57.104 [INFO] Pid: 29566 associated with [APVH_username_Suphp:]
2010-04-13 13:24:57.104 [INFO] ProcInfo Pid: -1, socket: /tmp/lshttpd/APVH_domain.com_Suphp.sock.316 
2010-04-13 13:24:57.104 [INFO] [APVH_username_Suphp:] pid list size: 0, pid stop list size: 0
2010-04-13 13:24:57.398 [INFO] Start listen socket [/tmp/lshttpd/APVH_domain.com_Suphp.sock.363].
2010-04-13 13:24:57.406 [INFO] [APVH_username_Suphp:] pid list size: 1 
2010-04-13 13:24:57.406 [INFO] [APVH_username_Suphp:] add child process pid: 29622

On high traffic sites and servers this fills the error_log file to 2GB in no time and it's mostly useless unless you're debugging an issue.

I imagine this might require some re-design of what is considered info, notice etc. but I think this would be beneficial to do in the long run.

[AndrewT]

I fully agree.

[anewday]

Same here.

[robfrew]

Count me in on this!

[mistwang]

We will change log level for those log messages to DEBUG