Closed
Description
So far as I am able to tell, making a change to any of journald's configuration files (/etc/systemd/journald.conf
, for example) requires subsequently running systemctl restart systemd-journald
in order for the changes to take effect. However, restarting the journald service appears to break logging for all other running services until those services are also restarted (journalctl -flu <service_name>
shows no new log lines post journald restart).
I'd like to request support for reloading journald configuration without restarting the process and breaking logging for other systemd services. I see this feature as rather critical. Without it, it's necessary for me to take servers out of service just to change the logging configuration.