ID: 38566 Updated by: [EMAIL PROTECTED] Reported By: noc at smartterra dot de -Status: Open +Status: Feedback Bug Type: Apache2 related Operating System: FreeBSD 5.3 PHP Version: 4.4.4 New Comment:
Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip Previous Comments: ------------------------------------------------------------------------ [2006-09-06 09:12:26] noc at smartterra dot de Hm, sometimes this bug is still present with my new setup: PHP Warning: Unknown(): SAFE MODE Restriction in effect. The script whose uid/gid is 0/0 is not al lowed to access /usr/home/phpissue owned by uid/gid 1025/1025 in Unknown on line 0 "Don't halloo till you're out of the wood!" :-( ------------------------------------------------------------------------ [2006-09-05 20:17:19] noc at smartterra dot de I set up a completly new system with FreeBSd 6.1, Apache 2.0.59 and PHP4.4.4 - it works for me without any problems. ------------------------------------------------------------------------ [2006-09-05 10:21:04] info at nrg-systems dot de We have the same PHP warning messages in our log files since we've upgraded from 4.3.11 to 4.4.2 (also with 4.4.3 and 4.4.4). It looks like as every file access (including static HTML pages and even images) from the Apache server results in this PHP message. But the files are delivered to the clients browser. Especially the part "in Unknown on line 0" is an evidence that the PHP check is called even for non-PHP scripts. ------------------------------------------------------------------------ [2006-08-24 09:24:17] noc at smartterra dot de I saved a copy here: http://smartterra.de/phpissue.html ------------------------------------------------------------------------ [2006-08-24 09:16:09] [EMAIL PROTECTED] >When it helps I can provide the complete output of phpinfo(). Put it somewhere in the net and paste the link here. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/38566 -- Edit this bug report at http://bugs.php.net/?id=38566&edit=1
