PHP 异常日志 error_log
PHP 错误日志 error_log1.php 友好记录错误日志(以日期为界限保存在不同的文件中)//创建log目录$destinati
PHP 错误日志 error_log
1.php 友好记录错误日志(以日期为界限保存在不同的文件中)
//创建log目录$destination = 'imember_'.to_date(get_gmtime(),"Ym");//创建错误日志保存路径if (!is_dir("D:/wamp/logs/".$destination)) {@mkdir("D:/wamp/logs/".$destination);@chmod("D:/wamp/logs/".$destination, 0777);}//im:记录php错误日志ini_set("display_errors",0);//不在页面显示错误信息error_reporting(E_ALL ^ E_NOTICE);//记录错误日志的级别ini_set( "log_errors", "On" );//打开错误日志ini_set( "error_log", "D:/wamp/logs/".$destination."/".date('d').".log");//设置保存错误日志的地址
2.error_log说明:
error_reporting() 设置 PHP 的报错级别并返回当前级别。
语法
error_reporting(report_level)
如果参数 level 未指定,当前报错级别将被返回。下面几项是 level 可能的值:
值 | 常量 | 描述 | 1E_ERRORFatal run-time errors. Errors that can not be recovered from. Execution of the script is halted2E_WARNINGNon-fatal run-time errors. Execution of the script is not halted4E_PARSECompile-time parse errors. Parse errors should only be generated by the parser8E_NOTICERun-time notices. The script found something that might be an error, but could also happen when running a script normally16E_CORE_ERRORFatal errors at PHP startup. This is like an E_ERROR in the PHP core32E_CORE_WARNINGNon-fatal errors at PHP startup. This is like an E_WARNING in the PHP core64E_COMPILE_ERRORFatal compile-time errors. This is like an E_ERROR generated by the Zend Scripting Engine128E_COMPILE_WARNINGNon-fatal compile-time errors. This is like an E_WARNING generated by the Zend Scripting Engine256E_USER_ERRORFatal user-generated error. This is like an E_ERROR set by the programmer using the PHP function trigger_error()512E_USER_WARNINGNon-fatal user-generated warning. This is like an E_WARNING set by the programmer using the PHP function trigger_error()1024E_USER_NOTICEUser-generated notice. This is like an E_NOTICE set by the programmer using the PHP function trigger_error()2048E_STRICTRun-time notices. PHP suggest changes to your code to help interoperability and compatibility of the code4096E_RECOVERABLE_ERRORCatchable fatal error. This is like an E_ERROR but can be caught by a user defined handle (see also set_error_handler())8191E_ALLAll errors and warnings, except level E_STRICT (E_STRICT will be part of E_ALL as of PHP 6.0)