[TYPO3-core] RFC: error logging for the Core

[Karsten Dambekalns]

Hi.

On Wednesday 04 January 2006 23:58, Michael Stucki wrote:
> instead! Bad that you perform the default log operation before checking for
> the hook (IMHO it should simply replace the built-in functionality).

+1

> I prefer these solutions in the following order:
>
> 1. Write the file manually:
>    Works everywhere just out-of-the box.
>
> 2. Call syslog()
>    I can setup syslog to log TYPO3 messages into a separate logfile - no
>    TYPO3 involved, only the facility that needs to be configured through
>    TYPO3_CONF_VARS.
>
> 3. Use error_log()
>    In my opinion, error_log() is probably useful for short time debugging,
>    but it is not helpful to be used as a permanent system log because of
>    endless-repeating syntax error reports.

I would prefer 1, 3, 2. If I set PHP to log errors to a file or to syslog, 
then it would (IMHO) be confusing if PHP errors go somewhere and TYPO3 errors 
go somewhere else (depending on configuration). Using error_log() and having 
PHP log to syslog gives me both sources in one log file.

The syslog() variant (which has the advantage of being able to define the log 
facility) could be optional.

Either way, it would be nice to have this, but it will only be really useful, 
if it widely deployed throughout the core (and extensions).

Regards,
Karsten
-- 
Karsten Dambekalns
TYPO3 Association - Active Member
http://association.typo3.org/