[PHP-DEV] Error_log

2003-03-06 Thread John Coggeshall

Is there any reason we are still supporting PHP3 for error_log?
Specifically that TCP/IP stuff. I was looking at error_log and I was
wondering if anyone had a good objection to me submitting a patch for it
to:

define constants ERRORLOG_SYSLOG, ERRORLOG_EMAIL, ERRORLOG_FILE ..
It's really ugly having hard-coded ints

Getting rid of message_type = 2 (TCP/IP logging) since it doesn't
work anymore, make it the same as 3 (write to file) and throw a notice
if type 3 is used (but still work). 

John


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP-DEV] error_log() and output buffering

2002-08-26 Thread Sebastian Bergmann

Sebastian Bergmann wrote:
 Marcus Boerger wrote:
 To have ob_start() working again i first allowed
 array(object,method).

 Thanks, XML_Transformer works again with HEAD.

  With HEAD, the server offers me the script's result as a download in 
  both Mozilla 1.0.0 and MSIE 6 when XML_Transformer runs in debug mode.

  If XML_Transformer's debug mode is disabled, it works just fine.

  The only difference between the two modes is that in debug mode
  error_log() is used to collect debugging information.

  Is error_log() affected by any of the recent output buffering patches?

-- 
  Sebastian Bergmann
  http://sebastian-bergmann.de/ http://phpOpenTracker.de/

  Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] error_log() and output buffering

2002-08-26 Thread Marcus Börger

At 17:16 26.08.2002, Sebastian Bergmann wrote:
Sebastian Bergmann wrote:
  Marcus Boerger wrote:
  To have ob_start() working again i first allowed
  array(object,method).
 
  Thanks, XML_Transformer works again with HEAD.

   With HEAD, the server offers me the script's result as a download in
   both Mozilla 1.0.0 and MSIE 6 when XML_Transformer runs in debug mode.

   If XML_Transformer's debug mode is disabled, it works just fine.

   The only difference between the two modes is that in debug mode
   error_log() is used to collect debugging information.

   Is error_log() affected by any of the recent output buffering patches?

Which SAPI do you use mod_apache or cgi?


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] error_log() and output buffering

2002-08-26 Thread Sebastian Bergmann

Marcus Börger wrote:
 Which SAPI do you use mod_apache or cgi?

  CGI

-- 
  Sebastian Bergmann
  http://sebastian-bergmann.de/ http://phpOpenTracker.de/

  Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] error_log() and output buffering

2002-08-26 Thread Marcus Börger

At 17:16 26.08.2002, Sebastian Bergmann wrote:
Sebastian Bergmann wrote:
  Marcus Boerger wrote:
  To have ob_start() working again i first allowed
  array(object,method).
 
  Thanks, XML_Transformer works again with HEAD.

   With HEAD, the server offers me the script's result as a download in
   both Mozilla 1.0.0 and MSIE 6 when XML_Transformer runs in debug mode.

   If XML_Transformer's debug mode is disabled, it works just fine.

   The only difference between the two modes is that in debug mode
   error_log() is used to collect debugging information.

   Is error_log() affected by any of the recent output buffering patches?


In mod_apache this maps to either aplog_error() or to log_error() which are
apache functions.

In cgi this simply maps fprintf(stderr,...). I must see if this can cause the
problem...that'll take some time becaause i have to change my sapi...

marcus


-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] error_log()

2002-08-26 Thread Marcus Boerger

During analysis of error_log i remembered it's lack to be integrated in
php_error() mechanism.

We could implement behaviour 5 and emit an E_USER_xxx message
with the name of the user function being executed.

Any comments?

marcus



-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




Re: [PHP-DEV] error_log() and output buffering

2002-08-26 Thread Sebastian Bergmann

Marcus Börger wrote:
 In cgi this simply maps fprintf(stderr,...). I must see if this can 
 cause the problem.

  Just tested it with the Apache 2.0 Filter SAPI and it works fine.
  I guess this answers the question of whether or not it's sapi/cgi
  related.

-- 
  Sebastian Bergmann
  http://sebastian-bergmann.de/ http://phpOpenTracker.de/

  Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/

-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php




[PHP-DEV] error_log doesn't use file locking

2001-01-27 Thread Ivan Petrovic

Bug or feature in all php versions?

If couple of users trigger error_log() in the same time - the output file
becomes garbled.

It should be nice to have flock with timeout. Is there some kind of alarm
(like in C) suitable for this?


Regards
Ivan






-- 
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]