Difference between revisions of "Limit the size of .log files & the journal"

Line 13:

==== The first topic on this page will briefly cover the '''systemd journal''' ====

The systemd journal has taken the place of log files though it ~~has an option for~~ the standard type log files ~~to be~~ created & maintained in the ~~usual fashion~~, ~~which is~~ the ~~way that Manjaro does it~~. Unfortunately there are still ~~plenty of~~ bugs in systemd & using the method presented below, for limiting the size of the /var/log/journal/* works for some but not for others, it also works more effectively for some & only somewhat effectively for others, meaning it will limit the size of the journal, but not to the limit that you set? As systemd's development continues this problem should eventually change.

The systemd journal has taken the place of log files though it will happily run in parallel with the standard type log files. These are still created & maintained by default in Arch & Manjaro, which means that even if you delete syslog-ng & all of the /var/log/*log files on reboot you will find the log files have been automatically created again, this will change in the future.

==== On limiting the size of the journal ====

Unfortunately there are still bugs in systemd & using the method presented below, for limiting the size of the /var/log/journal/* works for some but not for others, it also works more effectively for some & only somewhat effectively for others, meaning it will limit the size of the journal, but not to the limit that you set? Or, as in my case it will allow the journal to grow beyond the set limit & then a few days later it will bring the journal's size down again, below the limit. As systemd's development continues this problem should eventually change.

==== The second topic will cover handling log files ====

@@ Line 13: / Line 13: @@
 ==== The first topic on this page will briefly cover the '''systemd journal''' ====
-The systemd journal has taken the place of log files though it has an option for the standard type log files to be created & maintained in the usual fashion, which is the way that Manjaro does it. Unfortunately there are still plenty of bugs in systemd & using the method presented below, for limiting the size of the /var/log/journal/* works for some but not for others, it also works more effectively for some & only somewhat effectively for others, meaning it will limit the size of the journal, but not to the limit that you set? As systemd's development continues this problem should eventually change.
+The systemd journal has taken the place of log files though it will happily run in parallel with the standard type log files. These are still created & maintained by default in Arch & Manjaro, which means that even if you delete syslog-ng & all of the /var/log/*log files on reboot you will find the log files have been automatically created again, this will change in the future.
+<br clear="all"/>
+==== On limiting the size of the journal ====
+Unfortunately there are still bugs in systemd & using the method presented below, for limiting the size of the /var/log/journal/* works for some but not for others, it also works more effectively for some & only somewhat effectively for others, meaning it will limit the size of the journal, but not to the limit that you set? Or, as in my case it will allow the journal to grow beyond the set limit & then a few days later it will bring the journal's size down again, below the limit. As systemd's development continues this problem should eventually change.
 ==== The second topic will cover handling log files ====