Package: bsdutils Version: 1:2.26.2-6 Not affected: 1:2.25.2-6
This is a regression from jessie, present in sid. Steps to reproduce: 0. Ensure a syslog daemon is not running. 1. Run "logger". Expected behaviour: block on stdin Actual behaviour: exit with status 0 I can easily reproduce this using schroot against jessie vs. sid. Note that if systemd is present then the problem does not occur - I presume because systemd-journald is listening on /dev/log. So this affects chroots and sysvinit-core only. This is a problem because a utility that has its status or error output piped to logger fails due to a broken pipe when it tries to write status to stdout when logger exits. My expectation is that this is a common use case of logger on stdin and I can't think of any other easy way to arrange things such that logger still effectively no-ops in a minimal environment with no running syslog daemon. This causes mysql-server-5.6 to fail piuparts right now (bug 787864) since in piuparts' chroot there is no running syslog daemon. Alternatively, should we be doing something else to log output instead such that it doesn't fall over when syslog is unavailable? Thanks, Robie
signature.asc
Description: Digital signature
