dave at lambsys.com
Sat Mar 24 18:44:18 PDT 2012
Thanks Lennart. I was running v40. Upgrading to v44 seems to have fixed
On 03/21/2012 09:18 PM, Lennart Poettering wrote:
> On Wed, 21.03.12 20:47, David Lambert (dave at lambsys.com) wrote:
>> I am still having problems with being unable to control the growth
>> the systemd journal log files, despite various attempts at imposing
>> limits in systemd-journald.conf (attached). As I am running on an
>> extremely resource limited embedded system, I would like to know if
>> there is any other way to control or disable systemd-journal.
> This is the only option you should use (assuming you want volatile
> logging only), leave all others commented. If you want persistant
> logging use SystemMaxUse=1M instead and create the dir
> Also, you need v44 for this to work correctly.
> There's currently no way to turn off journald entirely, but it's on the
> TODO list. When that's done you can tell journald to output to kmsg (via
> systemd_journal.forward_to_kmsg=yes on the kernel cmdline) and turn both
> the volatile and the persistant journal files off.
More information about the systemd-devel