SOURCES: php-cli.ini - sanitize error output (display_errors=stderr, log_er...

[glen]

Author: glen                         Date: Mon Jan  5 14:31:38 2009 GMT
Module: SOURCES                       Tag: HEAD
---- Log message:
- sanitize error output (display_errors=stderr, log_errors=off) so errors are displayed only once to stderr in CLI SAPI

---- Files affected:
SOURCES:
   php-cli.ini (1.3 -> 1.4) 

---- Diffs:

================================================================
Index: SOURCES/php-cli.ini
diff -u SOURCES/php-cli.ini:1.3 SOURCES/php-cli.ini:1.4
--- SOURCES/php-cli.ini:1.3	Wed May  9 10:25:06 2007
+++ SOURCES/php-cli.ini	Mon Jan  5 15:31:32 2009
@@ -18,10 +18,22 @@
 ; instead (see below).  Keeping display_errors enabled on a production web site
 ; may reveal security information to end users, such as file paths on your Web
 ; server, your database schema or other information.
-display_errors = On
+;
+; possible values for display_errors:
+;
+; Off        - Do not display any errors
+; stderr     - Display errors to STDERR (affects only CGI/CLI binaries!)
+; stdout (On) - Display errors to STDOUT
+display_errors = stderr
 
-[Session]
-session.save_path         = /tmp    ; argument passed to save_handler
-                                    ; in the case of files, this is the
-                                    ; path where data files are stored
+; Log errors into a log file (server-specific log, stderr, or error_log (below))
+; As stated above, you're strongly advised to use error logging in place of
+; error displaying on production web sites.
+;
+; In CLI it's pointless to log it as we already print them to stderr.
+log_errors = Off
 
+[Session]
+; argument passed to save_handler in the case of files, this is the
+; path where data files are stored.
+session.save_path = /tmp
================================================================

---- CVS-web:
    http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SOURCES/php-cli.ini?r1=1.3&r2=1.4&f=u