I see what people thought I was saying. Yes, it’s open source and doesn’t taint the kernel. I’m saying the way it works is obfuscated or complicated for the user. You shouldn’t have to run binaries to figure what the logs say. The logs should be in text.
As a selfhoster, the way systemd does logs is great, I love it.
Oh, and also if you want you can tell systemd to save the logs to files, it’s an option
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
I see what people thought I was saying. Yes, it’s open source and doesn’t taint the kernel. I’m saying the way it works is obfuscated or complicated for the user. You shouldn’t have to run binaries to figure what the logs say. The logs should be in text.
As a selfhoster, the way systemd does logs is great, I love it. Oh, and also if you want you can tell systemd to save the logs to files, it’s an option
Please advise on the second portion.
I e never done this but it should work. https://unix.stackexchange.com/questions/321709/redirect-systemd-service-logs-to-file
See this