One for your browser and IDE and the other for viewing the log files update live as you go.

dating ru massege-19dating ru massege-71dating ru massege-19

Command line PHP falls back to stderr because the log file is (usually) only writable by the webserver. If multiple scripts share the same log file, but run as different users, whichever script logs an error first owns the file, and calls to error_log() run as a different user will fail *silently*!

Nothing more frustrating than trying to figure out why all your error_log calls aren't actually writing, than to find it was due to a *silent* permission denied error!

This is bad if all you want to do is log information.

However you can simply log to stderr however you will have to do all message assembly: Log To Apache($Message) "It appears that the system log = stderr if you are running PHP from the command line"Actually, it seems that PHP logs to stderr if it can't write to the log file.

How much of a risk it is depends on how much and what type of information you are sending, but the mere act of sending an email when something happens (even if it cannot be read) could itself imply to a sophisticated hacker observing your site over time that they have managed to cause an error.

Of course, security through obscurity is the weakest kind of security, as most open source supporters will agree.when using error_log to send email, not all elements of an extra_headers string are handled the same way."From: " and "Reply-To: " header values will replace the default header values. Just add "Content-Type: text/html; charset=ISO-8859-1" into extra_header string.I'm sure this differs from OS to OS, but I have seen it die writing to ext2 under modern Linux systems.This had me hunting for a while till I figured this out.IE: ; Log errors to specified file.error_log = "c:\php\errorlog.txt"; Log errors to syslog (Event Log on NT, not valid in Windows 95).;error_log = syslog2) The IUSR account has write and modify permissions to e .