What I do is what bohoomil suggests and edit the /etc/systemd/journald.conf.. here are my settings, which don't actually disable journald from logging, since sometimes you do want that.
[Journal]
Storage=persistent
Seal=no
SystemMaxUse=50M
RuntimeMaxUse=50M
ForwardToSyslog=yes
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 daemon will still work however.
I use it on one machine in conjunction with syslog-ng: It allows me to keep the old logs and a few scripts I wrote to do some checking running.
The closest thing to disable would probably be to use 'volatile'.
That feature is very important for any network heavily relying on the Syslog; from security auditing, to gathering
business intelligence data, or simply monitoring for MCE/RAID/RAM failures. Because now you have this brand
new software forcing it self between Rsyslog or Syslog-NG and playing a proxy and if it crashes[1] there's nothing
you can do. It's also unknown how it will handle millions of messages passing through it (ie. web server page
views).
According to this[2] mailing list post it is on the TODO list, but desktops not servers seem to be the priority
in everything.
Edit: the new Journald corruption thread[3] is interesting in the context that Journald is still too new.
1. http://lists.freedesktop.org/archives/s … 04386.html
2. http://permalink.gmane.org/gmane.comp.s … devel/4693
3. https://bbs.archlinux.org/viewtopic.php?id=150442
There seems to be no way of disabling journald through journald.conf
You can't disable journald as far as I can tell. I mentioned using /etc/systemd/journald.conf to optimize the service instead...
]]>mask it, though I am unsure that would be wise.
So am I. A wiser approach seems to be editing '/etc/journald.conf' instead and changing the most performance critical values appropriately. 'man journald.conf' should help decide what to tweak.
]]>I am running Arch on a low spec machine, and I'd like to get rid of system logging.
I tried systemctl disable systemd-journald but the service comes back after reboot.
Have a good day.
]]>