Bug 1328780 - journald.conf - changed default for ForwardToSyslog parameter
Summary: journald.conf - changed default for ForwardToSyslog parameter
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Branislav Blaškovič
URL:
Whiteboard:
Depends On: 1285642
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 09:37 UTC by Marcel Kolaja
Modified: 2019-10-10 11:55 UTC (History)
16 users (show)

Fixed In Version: systemd-219-19.el7.8
Doc Type: Bug Fix
Doc Text:
In an earlier version, the default value of the ForwardToSyslog parameter was changed and was by default set to "no". Consequently, the rsyslog utility was by default reading data from journal through the imjournal plug-in, in which case forwarding to traditional syslog daemons was not affected. However, if the syslog daemon read messages through the /run/systemd/journal/syslog file, forwarding to traditional syslog daemons was turned off. This update sets the default value of ForwardToSyslog to "yes" to prevent the described behavior from occurring.
Clone Of: 1285642
Environment:
Last Closed: 2016-05-12 10:07:04 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2264101 0 None None None 2016-04-20 09:37:31 UTC
Red Hat Product Errata RHBA-2016:1026 0 normal SHIPPED_LIVE systemd bug fix update 2016-05-12 13:56:10 UTC

Description Marcel Kolaja 2016-04-20 09:37:22 UTC 
This bug has been copied from bug #1285642 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 3 Lukáš Nykrýn 2016-04-20 10:05:46 UTC 
https://github.com/lnykryn/systemd-rhel/commit/298dd4f0bf734002a4fc7f51e5a46216017db2f6
Comment 10 errata-xmlrpc 2016-05-12 10:07:04 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-1026.html
Note You need to log in before you can comment on or make changes to this bug.