3 ms·
That was the task for years for syslog services that dealt with it without issue.
by greatgib 2mo ago
That was the task for years for syslog services that dealt with it without issue.
- touisteur 2mo agorsyslog is an incredible piece of software. Every time I'm looking for something to do with logs, opening the docs or googling finds the feature for me and myriads alternatives. I know it still exists and use it heavily on any system I'm in charge of, but there's some regret at having a dual system with journalctl...
- giov4 2mo agoI can confirm this, used it for many years, 3 keywords: efficient, reliable, useful. all 3 missing on journald,in my experience i saw it inefficient also on configuration level, unreliable because of loosing loglines on crash or reboot and not useful since to look at logs i need 3 commands, verbose parameters and 5 google search to find them. syslog experience? very efficient also on heavy load production instances, never lost a log, pipe grep and jq and you have the info you need. so what I experienced is that a default linux install was shipping a rock solid logging system by default, reliable and usable and everybody knew what was where and you will find it. now i just have fancy stuff, units etc and lost all of that. no I dont need to tune config parameters on a default install to have working basic logging tnx.
- TylerE 2mo agoWHen I provisioned a mid-range dedicated box recently, I went FreeBSD almost entirely so as to not have to touch or deal with anything related to systemd, the worst the thing to ever happen to linux.
- microgpt2 2mo agoGentoo also has a systemd-free option (and even if it didn't, you could make one because Gentoo is basically LinuxFromScratch)
- boobsbr 2mo agoWHAT R UR CFLAGS??!?
- actionfromafar 2mo agohttps://www.devuan.org/ https://www.devuan.org/
- hdgvhicv 2mo agoThe problem with systemd is the scale. Some of it is fine, some of it is actually quite good. But other areas are just replacing existing systems with things worse for the majority of traditional users. Logging, time and dns come to mind.
- sam_lowry_ 2mo agosystemd-boot ia actually one of the rare components that are pleasant to work with.
- otterley 2mo ago> syslog experience? very efficient also on heavy load production instances, never lost a log, You’re lucky. The original syslog protocol was fire-and-forget UDP (which I believe is still the default, though it’s been ages and I could be wrong) and the daemon was single threaded. I/O or CPU starvation could easily lead to dropped logs.
- zh3 2mo agoAnd still does. I generally replace journald with rsyslogd on systemd setups.
- otterley 2mo agoThe syslog architecture never had a filter component in the middle that could drop logs before they reached syslogd.
- Hundredth0006 2mo agosyslog wasn't dealing with it because all of this output was written in .xsession-errors in user's homedir (which was not rotated btw)