6 ms·
“I wish systemd would get over its thing about syslog”
- liveoneggs 12y agoYou can sub syslog with any component systemd has cannibalized and write the exact same article. That's what the whole argument was all about.
- feld 12y agoThe people who say "it's not that bad" are those who haven't interacted with these extremely reliable and integral parts of a Unix system for years and years and understand the ramifications of bad behavior.
- _delirium 12y agoThe author of this article has done so, and seems to think that until this syslog interaction it hasn't been too bad: > One of systemd's strengths until now has been that it played relatively well (sometimes extremely well) with existing systems, warts and all.
- feld 12y agoSo this means any logging/auditing software that requires the data to be sourced from syslog is unreliable. This kind of behavior would make an auditor's head spin.
- richardwhiuk 12y agoIf you are auditing systems based on systemd (or sysvinit or makefiles or upstart or launchd) then you are probably doing it wrong anyway
- unethical_ban 12y agoIf you build a custom logger into a startup/scheduler instead of using the existing logging component, you're doing it wrong. Really, if you're not using the logging mechanism to check a system, what are you using?
- icebraining 12y agoSo systemd has a few bugs that affects its interaction with syslog. I see nothing to indicate this is specifically because of some ill will towards it. Is there a bug report with a dismissive reply? Or one being ignored? (I do agree that it shows that systemd is too immature for critical production environments)
- JoshTriplett 12y ago> Is there a bug report with a dismissive reply? Or one being ignored? That's always my reaction to blog posts like this as well. A blog post is not a bug report. Given the mentioned bug in the systemd/syslog interaction that made it into RHEL, there should be a bug in the RHEL bug-tracker, and I'd hope it'd be a high priority one.
- cpncrunch 12y agoI think the issue is just stability in general. I just moved to a new server recently, and I decided to go with CentOS 6 instead of 7, as people were reporting that CentOS 7 is just a little less stable in general than 6. (Although systemd probably isn't entirely responsible for the lower stability in CentOS 7, it probably is one of the major changes in CentOS 7 so it likely takes a good share of the blame). You always end up with bugs in released software, even CentOS. Some bugs only show up in certain situations, and might be difficult to track down. The only way to give a good guarantee of stability is for a large number of people to use the damn thing for years on end!
- onli 12y agoIf systemd had no ill will towards syslog, there would be no journald.
- boklm 12y agoNo, journald has its own benefits. Creating an alternative to some software doesn't mean you have ill will towards it.
- erikb 12y agoI only watched part of the systemd wars from the side line and to this day I haven't come up with a reasonable solution. Both sides have reasonable arguments. Saying that a tool is unsupportive towards another tool because in the interaction two irregular bugs happen sounds like a weak claim though. Don't all tools have bugs? What makes these two special?
- digi_owl 12y agoAnd the PR division is already in action in the comments...
- pavanky 12y agoThe PR division is the entire userbase of Fedora, Arch and a few other distributions who have been using it for years without any issues.
- pessimizer 12y agoNo, it's not. Just because you use Fedora or Arch doesn't imply that you aggressively support every architectural choice that they have made.
- deelowe 12y agoI use arch and still despise it. The reduced boot time isn't worth the headache the overly complex systemd suit of tools has introduced. BSD might have some issues, but it worked very well for my use-cases.
- heinrich5991 12y agoTo me systemd is not the reduced boot time but the simplified service management.
- thescribe 12y agoTo me, as an Arch user, sytemd has been responsible for a series of btrfs kernel panics. I'll probably switch to Gentoo just to not have to deal with working around journald the next time I have a choice of distribution.
- vezzy-fnord 12y agoI think journald is by far the buggiest component systemd has. Log corruptions, the dubious Forward Secure Sealing mechanism, journal file fragmentation, the gateway daemon, coredump hooks. There's been several CVEs for it, too. Of course, you cannot disable it without source code modification. Quoting from the systemd wiki [1]: Note that it is now the journal that listens on /dev/log, no longer the BSD syslog daemon directly. If your logging daemon wants to get access to all logging data then it should listen on /run/systemd/journal/log instead via the syslog.socket unit file that is shipped along with systemd. On a systemd system it is no longer OK to listen on /dev/log directly, and your daemon may not bind to the /run/systemd/journal/syslog socket on its own. If you do that then you will lose logging from STDOUT/STDERR of services (as well as other stuff). ...unless your syslog implementation is socket activatable many services will not be able to log to your syslog implementation and early boot messages are lost entirely to your syslog implementation. So the fact that keeping your regular syslogd wasn't as simple as merely symlinking syslog.service was publicly known, but often overlooked by proponents during discussions. [1] https://wiki.freedesktop.org/www/Software/systemd/syslog/ https://wiki.freedesktop.org/www/Software/systemd/syslog/
- Qantourisc 12y agoThat's just bad, this is breaking API's ... suddenly other logging deamons need to change their code because systemd is squatting the log file ?!?
- smcleod 12y agoSystemD makes me feel weird. When I boot Debian 8 (which has systemd) I'm amazed how quickly it boots. Systemd units are nice. SysVinit was a mess. I wish I could interrupt stuck processes when booting / shutting down: http://i.imgur.com/a4ImjAk.jpg http://i.imgur.com/a4ImjAk.jpg When someone comments about how overly complex and controlling systemd is for an init system, I think of all the hideous shell scripts that don't talk to their neighbors which end up forming most the sysvinit boot process on many distros (in the past?). I wish there was something [lighter|simpler|more portable|more unix] than systemd. Every time I seed something [good|bad] about systemd it makes me want to [comment|upvote|walk away].
- digi_owl 12y agoThere have been several over the years, but none of them had RH riding shotgun.
- deleted 12y ago[deleted]
- vezzy-fnord 12y agoI wish there was something [lighter|simpler|more portable|more unix] than systemd. Your best bets are probably s6 or nosh. If you want just a service framework without init, then you can look at OpenRC, too. http://skarnet.org/software/s6/ http://skarnet.org/software/s6/ http://homepage.ntlworld.com/jonathan.deboynepollard/Softwares/nosh.html http://homepage.ntlworld.com/jonathan.deboynepollard/Softwar...
- mrmondo 12y agoThanks for the links - I'm sticking with Debian for now so I guess I'm using systemd for the foreseeable future there, which I [do|dont] have a problem with. systemd hasn't failed me yet - it really does just make me feel 'weird'.
- anonbanker 12y ago
- RexRollman 12y agoThe whole blog is interesting to read. Thanks OP.
- LinuXY 12y agoWhile I agree that systemd does not play nicely with syslog, you quickly realize that journald can be exported as JSON, filtered, described as time ranges, chunked and easily imported into ELK. My users (mainly developers) with less sed/awk fu have come to rely on these features heavily. I'm not really sure what there is to miss about syslog or syslog-ng when you have a robust ELK+journald system.
- rwmj 12y agoUnfortunately it's also very slow. Text files don't have the many advantages you outline, but in everyday use they are much faster than the C journal API.