| |||||||||||||
Poettering: The Biggest MythsPoettering: The Biggest MythsPosted Jan 28, 2013 3:38 UTC (Mon) by zlynx (subscriber, #2285)In reply to: Poettering: The Biggest Myths by HelloWorld Parent article: Poettering: The Biggest Myths
I *have* seen a dbus daemon get wedged. It was a few years ago and there may have been a kernel bug involved.
It definitely had messages waiting to process but it was stuck in a poll somehow.
(Log in to post comments)
Poettering: The Biggest Myths Posted Jan 29, 2013 9:05 UTC (Tue) by ovitters (subscriber, #27950) [Link]
In addition to what you said: Every so often dbus has security bugs. No software is without bugs, but at least the heavy usage of dbus ensures that at least a lot of bugs have been caught.
Alternative would be to make something like dbus yourself. That still will have bugs, could potentially have sscurity issues, etc. Maybe would be smaller than dbus, but then also would not have all the support that dbus has.
In short: No clue what is better (roll your own vs rely on dbus), but disagree with people who suggest dbus is "obviously wrong" (to be clear: do not mean you :)).
Poettering: The Biggest Myths Posted Jan 29, 2013 9:25 UTC (Tue) by nix (subscriber, #2304) [Link]
There was another recent bug that might have had the same effect. Same symptoms, poll()ers and select()ers on localhost got stuck after a while.
TBH, if something like that breaks, you're lucky to have a system at all. Those syscalls are *so* widely used...
|
|||||||||||||