β² 797 βΌ This guyβs a real Upstart if you ask me (thelemmy.club) submitted 3 weeks ago by cannedtuna@lemmy.world to c/linuxmemes@lemmy.world 184 comments fedilink hide all child comments
[β] Blue_Morpho@lemmy.world 0 points 3 weeks ago (2 children) It's not the binary. It's that the logs it writes are in binary so can't be read without a program. permalink fedilink source parent hideshow 4 child comments replies: [β] hirihit640@sh.itjust.works 7 points 3 weeks 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 permalink fedilink source parent hideshow 2 child comments replies: [β] Illecors@lemmy.cafe 2 points 3 weeks ago (2 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [β] hirihit640@sh.itjust.works 4 points 3 weeks 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 permalink fedilink source parent hideshow 2 child comments replies: [β] Illecors@lemmy.cafe 0 points 3 weeks ago (1 child) Why would I ever use a text editor? I think our approaches to viewing logs are fundamentally different. permalink fedilink source parent hideshow 2 child comments replies: [β] hirihit640@sh.itjust.works 2 points 3 weeks ago 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. permalink fedilink source parent [β] esc@piefed.social 1 point 3 weeks ago You can read systemd logs with strings program (part of binutils). Even if the file itself corrupted due to a crash. permalink fedilink source parent [β] Viceversa@lemmy.world 5 points 3 weeks ago* You can't read a text file without a program either. permalink fedilink source parent
[β] hirihit640@sh.itjust.works 7 points 3 weeks 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 permalink fedilink source parent hideshow 2 child comments replies: [β] Illecors@lemmy.cafe 2 points 3 weeks ago (2 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [β] hirihit640@sh.itjust.works 4 points 3 weeks 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 permalink fedilink source parent hideshow 2 child comments replies: [β] Illecors@lemmy.cafe 0 points 3 weeks ago (1 child) Why would I ever use a text editor? I think our approaches to viewing logs are fundamentally different. permalink fedilink source parent hideshow 2 child comments replies: [β] hirihit640@sh.itjust.works 2 points 3 weeks ago 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. permalink fedilink source parent [β] esc@piefed.social 1 point 3 weeks ago You can read systemd logs with strings program (part of binutils). Even if the file itself corrupted due to a crash. permalink fedilink source parent
[β] Illecors@lemmy.cafe 2 points 3 weeks ago (2 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [β] hirihit640@sh.itjust.works 4 points 3 weeks 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 permalink fedilink source parent hideshow 2 child comments replies: [β] Illecors@lemmy.cafe 0 points 3 weeks ago (1 child) Why would I ever use a text editor? I think our approaches to viewing logs are fundamentally different. permalink fedilink source parent hideshow 2 child comments replies: [β] hirihit640@sh.itjust.works 2 points 3 weeks ago 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. permalink fedilink source parent [β] esc@piefed.social 1 point 3 weeks ago You can read systemd logs with strings program (part of binutils). Even if the file itself corrupted due to a crash. permalink fedilink source parent
[β] hirihit640@sh.itjust.works 4 points 3 weeks 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 permalink fedilink source parent hideshow 2 child comments replies: [β] Illecors@lemmy.cafe 0 points 3 weeks ago (1 child) Why would I ever use a text editor? I think our approaches to viewing logs are fundamentally different. permalink fedilink source parent hideshow 2 child comments replies: [β] hirihit640@sh.itjust.works 2 points 3 weeks ago 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. permalink fedilink source parent
[β] Illecors@lemmy.cafe 0 points 3 weeks ago (1 child) Why would I ever use a text editor? I think our approaches to viewing logs are fundamentally different. permalink fedilink source parent hideshow 2 child comments replies: [β] hirihit640@sh.itjust.works 2 points 3 weeks ago 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. permalink fedilink source parent
[β] hirihit640@sh.itjust.works 2 points 3 weeks ago 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. permalink fedilink source parent
[β] esc@piefed.social 1 point 3 weeks ago You can read systemd logs with strings program (part of binutils). Even if the file itself corrupted due to a crash. permalink fedilink source parent
[β] Viceversa@lemmy.world 5 points 3 weeks ago* You can't read a text file without a program either. permalink fedilink source parent
