Timeline for How to clear journalctl
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 7, 2022 at 19:22 | history | edited | Caleb | CC BY-SA 4.0 |
added 132 characters in body
|
| Oct 10, 2019 at 7:15 | history | edited | Cristian Ciupitu | CC BY-SA 4.0 |
added link to man page
|
| Apr 13, 2018 at 9:37 | comment | added | x-yuri |
Also, one may specify SystemKeepFree=1G, or something along those lines. In any case, logs are not supposed to exceed 4G ("each value is capped to 4G").
|
|
| Mar 29, 2018 at 13:08 | comment | added | joelostblom |
To clean logs after a period of time rather than when they reach a certain size, you can set the parameter MaxRetentionSec instead of SystemMaxUse. See man journald.conf for more details.
|
|
| Jun 27, 2014 at 15:57 | comment | added | anlar | It may be not typical situation but sometimes it is necessary to delete old logs due to some systemd's bugs, e.g. bbs.archlinux.org/viewtopic.php?pid=1173031#p1173031 | |
| Jun 27, 2014 at 12:19 | comment | added | Łukasz Zaroda | By safe, I mean that after clearing it will work as usual, just starting from the new place. | |
| Jun 27, 2014 at 12:17 | comment | added | Caleb | @ŁukaszZaroda In that case you are going to have to define "safe". Normally "I want to blow away something that a daemon is configured to keep" is incompatible with "safe". If you want to force it just shut down the service and zero out the log files. If you want it to work normally you should define the parameters in your question better. What do you mean by "safe"? | |
| Jun 27, 2014 at 12:08 | comment | added | Łukasz Zaroda | Ok, but there are also untypical situations. I know that most of them is just aesthetics as a reason, but aesthetics is a valid reason for human being ;) . | |
| Jun 27, 2014 at 11:59 | history | edited | Caleb | CC BY-SA 3.0 |
deleted 15 characters in body
|
| Jun 27, 2014 at 11:52 | history | answered | Caleb | CC BY-SA 3.0 |