Here is a pstack of the dbus process in question 425: /usr/lib/dbus-daemon --system feef1687 __pollsys (82eb4e8, fa, 8047968, 0, 82cafd8, fef7f000) + 7 fee97824 poll (82eb4e8, fa, 3a4e, 8096318, 80c4f1c) + 4c 08096330 _dbus_poll (82eb4e8, fa, 3a4e, 8047a00) + 24 08098ccb _dbus_loop_iterate (80bf1b0, 1, 0, 809904e) + 32f 0809907e _dbus_loop_run (80bf1b0) + 3e 08078e8c main (2, 8047e90, 8047e9c, 8047e4c) + 7e8 080665bd _start (2, 8047f20, 8047f35, 0, 8047f3e, 8047f56) + 7d
Let me know if there is anything else I an dig up. Karl > > Karl: > > Many desktop applications require dbus-daemon, and > you will likely > find that the desktop doesn't work at all if you > disable it. I suspect > if you restart the service, that it will return to > normal CPU usage. > > If it is consuming 100% of a CPU, then this is a bug. > If you could > rovide a stack trace of the process via pstack, that > would help to > debug the problem. > > Brian > > > I'm running a 110 SUNRay session on it on a dual > quad core 64GB box. Things seem to be going ok. > > > > However I noticed that dbus-daemon seems to use > using 1 CPU core at 100%. > > > > What happens if I disabled the dbus-daemon? Will > the cups print dialog boxes stop working? > > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org -- This message posted from opensolaris.org
