Control: tags -1 + upstream confirmed Control: fixed -1 2.25.2-6 Hello Robie Basak.
Thanks for your bug report. On Thu, Jul 02, 2015 at 03:47:53PM +0100, Robie Basak wrote: > 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: jessie = v2.25.2 sid = v2.26.2 > > 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. I've bisected the git history and the change of behaviour seems to have been introduced in: https://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/misc-utils/logger.c?id=1d57503378bdcd838365d625f6d2d0a09da9c29d I'm adding Sami Kerola to CC and hoping he has time to look into this (which I don't have right now). > > 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? > Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
