#26989 [Opn->Bgs]: logfile ownership as root on extension loading failure

ID: 26989 Updated by: iliaa@php.net Reported By: david dot morel at amakuru dot net -Status: Open +Status: Bogus Bug Type: Apache related Operating System: Linux (homebrew) PHP Version: 4.3.4 New Comment: Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php This is to be expected. Previous Comments: ------------------------------------------------------------------------ [2004-01-21 06:24:19] david dot morel at amakuru dot net Description: ------------ When using a logfile to record errors, if the logfile doesn't yet exist, and if an extension cannot be loaded properly, the startup message will be written in this newly created file as the owner of the top webserver process, root. So subsequent tries by child processes to write in this file fail and no error is recorded I guess the same would apply to any load-time source of error. Nice thing would be that the logging facility checks the euid and see if it is different from the one the server is supposed to run his childs with (IMHO). Reproduce code: --------------- 1) set log errors to true in php.ini 2) in extensions, add a bogus filename 3) delete previous error log 4) launch webserver server 5) extension loading failure appears in log, but child processes can't append anything. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=26989&edit=1