you are viewing a single comment's thread
view the rest of the comments
[โ€“] 4 points 14 hours ago (1 child)

Even systems that use text logs, compress logs using logrotate and you have to uncompress before you can read them. Also since the compressed tar.gz logs are a bunch of separate files, if you don't have an exact date of what you're looking for, you have to uncompress and search through all of them. I much prefer just using journalctl

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] 1 point 5 hours ago (1 child)

    I mean... zless and zgrep have been a thing since forever ago. And some distros ship with lessopen(?) preinstalled, so it's seemless.

    There are only so many times I'm willing to put up with lost logfile due to a crash. Logrotate wouldn't do this.

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] 2 points 4 hours ago (1 child)

    But then you aren't just using a text editor anymore. If you're willing to use programs like zless and zgrep, then you can just as easily use journalctl. And I've never lost a logfile before, over many years, so not to discredit your experience but at least in my experience journald has been an upgrade

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] 1 point 2 hours ago (1 child)

    Why would I ever use a text editor? I think our approaches to viewing logs are fundamentally different.

  • source
  • parent
  • hideshow 2 child comments
  • Well the original comment I responded to said

    It's not the binary. It's that the logs it writes are in binary so can't be read without a program.

    Of course, a text editor is also a "program", but I assumed they were saying they preferred plain text logs.

    If you aren't agreeing with them then you need to state your position more clearly when you hop in.

  • source
  • parent