Greg KH wrote: > On Fri, May 04, 2012 at 11:02:01AM -0700, Luca Barbato wrote: >> On 03/05/12 18:22, Mike Frysinger wrote: >>>> (As soon I have some time I might dabble with a dbus integration for mdev) >>> >>> we would have to make mdev available as a sep package then ... don't want >>> busybox itself linking against anything beyond the C library. >> >> The integration would be mdev -> shell -> dbus or mdev -> socket -> >> dbus. I consider dbus still not reliable for core services. > > When was the last time dbus crashed on you? > > And what would you consider "reliable" enough for "core services"? dbus > has proven itself over _many_ years to handle all of the issues that > something like this requires very well. It's a non-trivial thing to > implement and the authors of it have done a very good job, after > learning how to do it from other failed attempts at the same thing. > > And what are you going to do when dbus moves into the kernel itself > (hint, it will be there soon)? How are you going to not use it then? > > greg k-h > >
This question is not directed at me but I'll give a response to my experience a few months ago. I woke up to my system fans blowing like crazy. Trust me, if you can hear noise on a HAF-932, they are spinning pretty good. It was mostly air I was hearing but anyway. I use KDE and have Konsole open at all times. I switched to the desktop with it, after noticing on Gkrellm that my CPU was maxed out and that almost all my ram was in use and some swap too. I don't mean cached or anything either, I mean actively in use. At any rate, when it finally switched to the desktop with Konsole on it, which took a bit, I ran top. At the top for both CPU and memory usage was dbus. I tried to restart the dbus service, thinking it would kill it and restart without all the ram and CPU usage. I could then logout and back in, maybe. I never got my prompt back and it never showed dbus as stopped either. I then switched to a console. I did a 'rc boot' and it was slowly switching to it and did but it couldn't stop the dbus service. I just typed in reboot and let it restart from scratch. Was it dbus itself, I dunno for sure. I am sure it was dbus that was maxing out my CPU and ram. I did recompile dbus after the reboot and it has not done it since. If I could reproduce it or had more info, I would have mentioned it when it happened. I'm thinking rays from Mars or something. ;-) It wasn't hardware either. This system has been running fine ever since. By the way, I have 16Gbs of ram. If I recall correctly, dbus was using over 14Gbs of ram and something was using swap. Keep in mind, I had KDE running with Seamonkey, Konsole, Konqueror and a couple other apps open. I use about 1.5Gbs when my desktop is in normal use. Swappiness is set to 20. In other words, only use swap when it is getting deep. It was using half my swap so it must have been pretty deep. So, even dbus can have a bad day at times. Sure wish I knew what caused it tho. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
