35
Is it good practice to run a system without a syslog daemon?
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Aug 2024
35 points (94.9% liked)
Linux
48199 readers
1232 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
You dont need syslog. Journald is good enough for most systems.
I also don't like the duplication of logs in journald and syslog, so I always disable forwarding to syslog
What if I'm on another minimal distro, like Artix, that doesn't use systemd? Journald is a systemd thing, and I'm not going to install systemd on top of a perfectly good init system.
Use whatever that distro recommends then - which as far as I can tell seems to be
svlogdfor runit based systems. Though you should consult their documentation and make your own decision on which logger to use.