Alan Jenkins
ba30753899
If we have to force the logging to close the journal fd, then we can open any fallback log target. E.g. kmsg, if the target was the default JOURNAL_OR_KMSG. This is the behaviour I would expect from the documentation. I couldn't find any justification in the code, for why we would want to start dropping log messages instead of sending them to the fallback target. This means we will match the behaviour of processes which we fork and which set `open_when_needed`, and with generators - which use log_set_prohibit_ipc(true) - which we fork+exec during a reload. IMO this illustrates that the log_open/log_close interface is too clunky. So with the behaviour settled, I will refactor the interface in the next commit :).
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements are provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the HACKING file for information how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.