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