03.03.2016 11:55, Carlos E. R. пишет:
On 2016-03-03 08:29, Per Jessen wrote:
Carlos E. R. wrote:
In fact, reading (dumping) the systemd journal is terribly slow because (educated guess) heavy on disk fragmentation. Unless the HD is an SSD.
Yes, I remember reading something about at some point. I don't use the journal myself, I always run syslog-ng.
Me too. Well, rsyslog.
But I'd prefer not to have journal running.
You can't. All logging in systemd assumes journald is present. It is multiplexor that receives everything and can forward it to other receivers (gateways to remote logging are available as well).
Or at least impede some entries from going into it, like email or nntp.
No. Journald explicitly does not do filtering. What you can do is disable storage and use it only for multiplexing: Storage=none "none" turns off all storage, all log data received will be dropped. Forwarding to other targets, such as the console, the kernel log buffer, or a syslog socket will still work however. Defaults to "auto".