Req #67589 [NEW]: With --nodaemonize errors don't get into error_log directive

From: serge dot rivest at gmail dot com Operating system: Linux PHP version: Irrelevant Package: Output Control Bug Type: Feature/Change Request Bug description:With --nodaemonize errors don't get into error_log directive Description: ------------ When running php-fpm with --nodaemonize, error_log is not respected. Instead, messages appear on the console (assuming STDOUT). This is an issue since distro started to use upstartd and launch php-fpm this way: exec /usr/sbin/php5-fpm --nodaemonize --fpm-config /etc/php5/fpm/php-fpm.conf which means the output doesn't get written into what is defined in the configuration. Instead it ends up being caught by upstartd and dumped into something like: /var/log/upstart/php5-fpm.log Test script: --------------- $ /usr/sbin/php5-fpm --daemonize ... error_log directive is respected, all error / warning / notice / debug go into log file. $ /usr/sbin/php5-fpm --nodaemonize ... error_log is not respected. Debug and notice get out on STDOUT / STDERR. Expected result: ---------------- It would be better if the error_log directive was always respected or if there was a command line option to use to force logging to file instead of STDOUT when the --nodaemonize option is used. $ /usr/sbin/php5-fpm --nodaemonize --force-log or something the like, or simply duplicate to error_log and STDOUT. -- Edit bug report at https://bugs.php.net/bug.php?id=67589&edit=1 --