Your message dated Thu, 14 Mar 2019 23:23:06 +0100 with message-id <[email protected]> and subject line Re: Bug#924602: systemd - regression: syslog msg from units not routed according to StandardOutput= has caused the Debian Bug report #924602, regarding systemd - regression: syslog msg from units not routed according to StandardOutput= to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 924602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924602 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: systemd Version: 241-1 Severity: normal syslog messages from units are not longer routed according to the StandardOutput setting, but I don't see a new setting to change it. My test case is: /etc/systemd/service/test.service: | [Service] | ExecStart=/usr/local/bin/service-test | StandardOutput=journal+console /usr/local/bin/service-test: | #!/bin/bash | logger "message syslog" | echo message stdout | echo message stderr >&2 In Buster the following shows up in the journal: | Mär 14 20:54:24 debian-9 systemd[1]: Started test.service. | Mär 14 20:54:24 debian-9 root[738]: message syslog | Mär 14 20:54:24 debian-9 service-test[737]: message stdout | Mär 14 20:54:24 debian-9 service-test[737]: message stderr | Mär 14 20:54:24 debian-9 systemd[1]: test.service: Succeeded. But only the following on the console: | [ 56.224716] service-test[737]: message stdout | [ 56.268206] service-test[737]: message stderr The message written to syslog via logger is missing from the console output. In Stretch, the syslog message was sent to the console as well. This makes that a regression. Bastian -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.20.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
--- End Message ---
--- Begin Message ---On Thu, Mar 14, 2019 at 11:01:31PM +0100, Michael Biebl wrote: > I quickly tested a stretch VM and the message sent via syslog (logger) > does not show up on the console, so I don't quite understand the "not > longer" comment. You are right. After thinking about it again I found my error in the tests. Bastian -- Our missions are peaceful -- not for conquest. When we do battle, it is only because we have no choice. -- Kirk, "The Squire of Gothos", stardate 2124.5
--- End Message ---
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
