Description of problem: The journald.conf man page (as well as lots of hits on google) claim that setting Storage=none stops journald from creating logs, but continues to forward all messages to syslog, etc. This does not happen. Virtually nothing is showing up in /var/log/messages when running with Storage=none. It appears to be almost exclusively hardware-like info that is the kind of thing that shows up in dmesg. Nothing is being logged about new user sessions (which used to clutter things up something fierce), nothing is being logged about DHCP requests (which were also very common before). Version-Release number of selected component (if applicable): systemd-208-22.fc20.x86_64 rsyslog-7.4.8-1.fc20.1.x86_64 How reproducible: 100% Steps to Reproduce: 1. set Storage=none in /etc/systemd/journald.conf 2. reboot 3. observe lack of messages in /var/log/messages Actual results: Almost nothing logged Expected results: Same plain text logs as before, just no binary logs. Additional info:
Possibly this is just a doc problem. If I take the additional step of creating a file named /etc/rsyslog.d/sd-socket.conf and putting the line: $AddUnixListenSocket /run/systemd/journal/syslog into it, then the logging does work with Storage=none
That makes sense. With Storage=none rsyslog cannot read anything by itself. journald.conf(5) is not wrong, just misleading. "Forwarding" might still work, but rsyslog does not use "forwarding", but pulls by itself. We should add a note to explain this. Also, as of http://cgit.freedesktop.org/systemd/systemd/commit/?id=46b131574f, the additional step of turning ForwardToSyslog manually has to be taken. This should be documented too.
*** Bug 1177335 has been marked as a duplicate of this bug. ***
*** Bug 1205657 has been marked as a duplicate of this bug. ***
http://cgit.freedesktop.org/systemd/systemd/tree/man/journald.conf.xml?id=589532d0c61ecd667b0c840ec25faed076f2291e#n378 It should read "a journal file at all. So it will NOT work if", no?
Fixed.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.