Bug 1205657 - systemd journal does not respect ForwardToSyslog=no
Summary: systemd journal does not respect ForwardToSyslog=no
Keywords:
Status: CLOSED DUPLICATE of bug 1147651
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-25 12:21 UTC by Christian Stadelmann
Modified: 2015-05-06 18:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-06 18:33:16 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1147651 0 unspecified CLOSED DOC: Setting Storage=none in journald.conf does not work, since rsyslog no longer uses ForwardSyslog= 2021-02-22 00:41:40 UTC

Internal Links: 1147651

Description Christian Stadelmann 2015-03-25 12:21:41 UTC 
On F22 alpha according to /etc/systemd/journald.conf ForwardToSyslog defaults to "no". /var/log/messages is being filled with all messages going to journal. Manually setting ForwardToSyslog=no has no effect.

Version-Release number of selected component (if applicable):
systemd-219-9
Comment 1 Jan Synacek 2015-03-25 13:28:07 UTC 
This looks that it might have something to do with bz1147651.
Comment 2 Zbigniew Jędrzejewski-Szmek 2015-05-06 18:33:16 UTC 

*** This bug has been marked as a duplicate of bug 1147651 ***
Note You need to log in before you can comment on or make changes to this bug.