Bug #66239 [PATCH]: Fpm won't error_log to syslog, php works fine

Edit report at https://bugs.php.net/bug.php?id=66239&edit=1 ID: 66239 Patch added by: krakjoe@php.net Reported by: sjon at hortensius dot net Summary: Fpm won't error_log to syslog, php works fine Status: Open Type: Bug Package: FPM related Operating System: archlinux PHP Version: 5.5.6 Block user comment: N Private report: N New Comment: The following patch has been added/updated: Patch Name: fpm-syslog-bug.patch Revision: 1386331016 URL: https://bugs.php.net/patch-display.php?bug=66239&patch=fpm-syslog-bug.patch&revision=1386331016 Previous Comments: ------------------------------------------------------------------------ [2013-12-06 11:55:37] krakjoe@php.net The following patch has been added/updated: Patch Name: fpm-syslog-bug-alternate.patch Revision: 1386330937 URL: https://bugs.php.net/patch-display.php?bug=66239&patch=fpm-syslog-bug-alternate.patch&revision=1386330937 ------------------------------------------------------------------------ [2013-12-06 11:47:09] krakjoe@php.net Why depend on wp->config->chroot ? Can you think of a case where it is reasonable for "syslog" to be expanded ? ------------------------------------------------------------------------ [2013-12-06 09:52:20] tony2001@php.net But why do you change fpm_evaluate_full_path()? It's used everywhere and php_value/php_admin_value is just one use case. I believe you should be changing the checks in this 'if' instead: /* env[], php_value[], php_admin_values[] */ if (!wp->config->chroot) { ------------------------------------------------------------------------ [2013-12-06 08:04:36] krakjoe@php.net fpm fails to check for "syslog" before expanding the path, patch attached ------------------------------------------------------------------------ [2013-12-06 08:04:05] krakjoe@php.net The following patch has been added/updated: Patch Name: fpm-syslog-bug.patch Revision: 1386317045 URL: https://bugs.php.net/patch-display.php?bug=66239&patch=fpm-syslog-bug.patch&revision=1386317045 ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=66239 -- Edit this bug report at https://bugs.php.net/bug.php?id=66239&edit=1