Thanks, but all these "methods" require modification of the scripts 
already on the server, and it won't ensure any new script being written 
by a user on my system to comply.
Are you all saying that there are no logs kept by default of errors 
generated on php/mysql pages at all unless specifically coded? Wouldn't 
it be possible then in future PHP releases to have a "set_error_logging" 
directive in the php.ini file that will automatically run a wrapper 
function on all mysql_query() functions to do this kind of thing?

How are people out there managing the scripts/script errors caused  by 
users on their systems? Or is it a case of "handling the crisis when it 
You see, as administrator, I need to be able to quickly see who are 
coding in such a way as to leave security holes, or even worse, cause 
the server to crash due to poor coding. There are almost 1000 individual 
php files on my server, and it wouldn't be possible for me to scrutinize 
all of them to make sure they are OK.
Are there any admins out there that have policies about scripting 
practices on their systems; ie, checking a script from a user before it 
is allowed to be uploaded etc?


Richard Lynch wrote:

>>Hi, tried this on mysql list, no luck:
>>I want to be able to view a single log that contains the following:
>>IP of user : page_name (PHP only): time/date: MySQL query ( 'select * 
>>from xxx' etc.) : error msg from mysql/php if any
>>So it's almost a hybrid between apache and mysql with some extra's
>>I'm sure you all should see the benifit of this in troubleshooting and 
>>specially keeping track of who does what when it comes to PHP coding on 
>>ones server, specially with crappy code that kills the server.
>>Is something like this possible, already there?
>>PS, Running RedHat 7.0 with PHP4 and mysql 3.23.x
>if you can get everybody to use your own function to query the database.
>Or, you could use and
> and catch all errors thrown by all PHP code.
>Actually, to get the PHP page name and line number, set_error_handler is
>probably your best bet.

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to