this post was submitted on 01 Aug 2024
665 points (98.5% liked)

linuxmemes

21195 readers
283 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith
    zephyr
    rtxn
    665
    Remember to not to forget clearing your journal (lemmy.world)
    submitted 3 months ago by bali10050 to c/linuxmemes
    62 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Pacmanlives 3 points 3 months ago (1 children)

    Actually something I never dug into. But does logrotate no longer work? I have a bunch of disk space these days so I would not notice large log files

    [–] [email protected] 2 points 3 months ago* (last edited 3 months ago) (1 children)

    If logrotate doesn't work, than use this as a cronjob via sudo crontab -e Put this line at the end of the file:

    0 0 * * * journalctl --vacuum-size=1G >/dev/null 2>&1

    Everyday the logs will be trimmed to 1GB. Usually the logs are trimmed automatically at 4GB, but sometimes this does not work

    [–] [email protected] 5 points 3 months ago (1 children)

    If we're using systemd already, why not a timer?

    [–] [email protected] 3 points 3 months ago (1 children)

    Cron is better known than a systemd timer, but you can provide an example for the timer 😃

    [–] [email protected] 5 points 3 months ago* (last edited 3 months ago) (1 children)

    Really, the correct way would be to set the limit you want for journald. Put this into /etc/systemd/journald.conf.d/00-journal-size.conf:

    [Journal]
SystemMaxUse=50M

    Or something like this using a timer: systemd-run --timer-property=OnCalender=daily $COMMAND

    [–] [email protected] 3 points 3 months ago

    Thanks for this addition ☺️