On 12/23/25 8:57 AM, Tiago de Paula wrote:
The syslog.socket is for communication between journald and the
classic syslog implementation [1]. Syslog-ng has an automatic
integration with systemd and pulls logs from the journal by itself [2].
The Wiki says you don't even need "ForwardToSyslog=yes", although
I do that too, mostly to avoid missing any logs in syslog-ng. For my
setup, I have something like this:
```/etc/systemd/journald.conf.d/forward.conf
[Journal]
Storage=auto
SystemMaxUse=1G
RuntimeMaxUse=100M
MaxFileSec=1month
ForwardToSyslog=yes
```
And then my long-lived logs are managed by syslog-ng and logrotate.
[1]:
https://wiki.archlinux.org/title/Systemd/Journal#Journald_in_conjunction_with_syslog
[2]: https://wiki.archlinux.org/title/Syslog-ng#systemd/journald_integration
Thanks much for that info.
Still, I wish I knew why my syslog-ng setup stopped working. (And how to
revive it.)
DR
