| Summary: | journald.conf - changed default for ForwardToSyslog parameter | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Branislav Blaškovič <bblaskov> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.2 | CC: | adam.winberg, bblaskov, chorn, dmoessne, dshaw, fkrska, jscotka, juanluisvaladas, lnykryn, mnavrati, msekleta, pdwyer, sven, systemd-maint-list, systemd-maint, theinric |
| Target Milestone: | rc | Keywords: | Reopened, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1285642 | Environment: | |
| Last Closed: | 2016-05-12 10:07:04 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1285642 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-04-20 09:37:22 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 |