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:

| [Service]
| ExecStart=/usr/local/bin/service-test
| StandardOutput=journal+console
| #!/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

In Stretch, the syslog message was sent to the console as well.  This
makes that a regression.


-- Package-specific info:

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
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

Reply via email to