Req #78656 [Com]: Parse errors classified as highest log-level

Edit report at https://bugs.php.net/bug.php?id=78656&edit=1 ID: 78656 Comment by: sjon@php.net Reported by: erik at coretech dot se Summary: Parse errors classified as highest log-level Status: Open Type: Feature/Change Request Package: Scripting Engine problem Operating System: CentOS 7 PHP Version: 7.3.10 Block user comment: N Private report: N New Comment: I agree - this setup (by default) will cause any parse-error to be broadcasted (using wall) to all users on a shared development machine Previous Comments: ------------------------------------------------------------------------ [2019-10-09 11:53:12] erik at coretech dot se Description: ------------ Parse errors are classified as the highest log level (LOG_EMERG). This is problem since Centos/Fedora writes LOG_EMERG messages to all users: https://src.fedoraproject.org/rpms/rsyslog/blob/master/f/rsyslog.conf#_59 LOG_EMERG is described as: "system is unusable". A php-script with a parse error would not in most cases render the system unstable. At most LOG_ERR or LOG_CRIT would be more suitable. Fatal errors are classified as LOG_ERR. Why not make parse errors the same level? The source: https://github.com/php/php-src/blob/PHP-7.3/main/main.c#L1300 The commit that changed this: https://github.com/php/php-src/commit/3edf7d960cb14f2ee45944e7c567af92af25bda1 ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=78656&edit=1