Skip to main content


@:debian: πšœπšŽπš•πšŽπšŠ :fedora: To be fair, journalctl --since="[date]" --until="[date]" is pretty convenient, but I still wasn't able to figure out why all my websites hosted on this server were unreachable for 3 hours earlier today. πŸ€·β€β™‚οΈ
@argv minus one I see Lennart Poettering's defender has logged on. I guess that's my own fault for tagging my post, huh?
Not that journal is perfect, but I am not going to miss the mess of little log files, all alike. After being forced to work with systemd for the last ten years, I've come to the conclusion that it's not all bad.
@Peter Krefting I've put myself in this position so I hope that I will reach the same acceptance you're having. Changing habits is hard.
@argv minus one I just expressed my feeling in my post, if you take that as "nonsense", it's on you, buddy, now scram.
@Sarah Brown Circumstances have forced me to move server, so I figured I'd try to go with the systemd flow. Weirdly enough, it's harder than resisting it because of well-entrenched habits.
@Sarah Brown @Hypolite Petovan There seems a lot of that in Linux these days, especially with the systemd tendency to want to be ALL THE THINGS. I think you can still install a proper syslogd that will generate sensible log files but most people will go with the flow (and probably be upset they can’t find anything in the β€œjournal”)
@Alexandra Lanes @Sarah Brown The thing is, I don't know how to set up a proper syslogd either, so it ends up just being a question of habits, which isn't enough for me to justify doing the little legwork needed to stray away from vanilla Debian.
@Hypolite Petovan @Sarah Brown @Alexandra Lanes Hrm ... rsyslogd should be pretty easy to setup, even alongside journalthing...
⇧