Re: [PHP4BETA] Move php_log_err() to SAPI?

From: Date: Sat, 05 Feb 2000 01:34:42 +0000
Subject: Re: [PHP4BETA] Move php_log_err() to SAPI?
References: 1  Groups: php.version4 
Request: Send a blank email to php-version4+get-9842@lists.php.net to get a copy of this message
Well, if you run php interactively, you simply shouldn't set it up that way; Unless you actually want to use redirection to put the stderr data to one file and the HTML output to another. I wouldn't oppose to such a change (I think), but I don't think it's all that necessary. The only way to differentiate between CGI and command line is checking for certain environment variables. Zeev On Fri, 4 Feb 2000, Andrei Zmievski wrote: > On Sat, 05 Feb 2000, Sascha Schumann wrote: > > > Ok, my question still stands: is there any way for CGI binary to detect > > > that it's being run from the command-line instead of through the server? > > > > Where do you need to differentiate? > > I need to differentiate because when run in command-line mode we want to > only respect either log_errors or display_errors setting. If you respect > both then the error output looks like this: > > PHP Fatal error: Call to undefined function: session_se_cookie_params() in ./test.php on line > 4 > <br> > <b>Fatal error</b>: Call to undefined function: session_se_cookie_params() in > <b>./test.php</b> on line <b>4</b><br> > > > -Andrei > * Programming is an art form that fights back. * > -- Zeev Suraski <zeev@zend.com> http://www.zend.com/

« previous php.version4 (#9842) next »