- sanitize error output (display_errors=stderr, log_errors=off) so errors are display...

Changed files:
    php-cli.ini -> 1.4

diff --git a/php-cli.ini b/php-cli.ini
index 479be181f026bce9075387bee66cffbe9e25d811..fb73086a1de16048278f346aa6d5b02963313c32 100644 (file)
--- a/php-cli.ini
+++ b/php-cli.ini
@@ -18,10 +18,22 @@ register_argc_argv = On
 ; 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