Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 9
    journalctl: unrecognized option '--rotate' Commented Oct 7, 2018 at 12:22
  • 14
    while I get what the other answers are approaching (long term strategy) - the question is simple: how do you clear logs now (maybe you're not interested in the long term for your current task). This answers that question without making other assumptions and adds other great value to understanding journalctl. This should be the answer. Commented Oct 20, 2018 at 15:39
  • 5
    Original question was "how do I reset my logs for debugging purposes". This is the only answer that addresses that. And I'm really glad I found it. The rest are interesting journalctl factoids, but not answers to the questions. Commented Oct 25, 2019 at 19:08
  • 1
    Note that this is a one-off command. It sounded to me like it would permanently set the vacuum time to 1 second, but no, this just removes current logs without changing your configuration (which is what I wanted). Commented May 26, 2021 at 12:13
  • 1
    This appears to clear all systemd logs. How would you clear all logs pertaining to a particular service while allowing all other sevices to retain their log-entries? Commented Jun 20, 2022 at 6:34