kded4 lockup (which makes the desktop unusable so this is important)
Matthias Kretz
kretz at kde.org
Thu May 8 20:48:18 BST 2008
Thanks for the fix. It was driving me insane.
On Thursday 08 May 2008, Andreas Hartmetz wrote:
> I believe that we should still look for ways to make kded (way) more
> robust. Strange things will happen everytime one module takes down or,
> worse, locks up kded.
I agree that kded4 is too important to not have some safety net...
Should we create a kded4 watchdog? That checks (via dbus) whether it is still
running or locked up?
Could the watchdog also be a thread in kded4? In that case I think it could
only catch lockups and then kill itself. Could it schedule a restart of
kded4?
--
________________________________________________________
Matthias Kretz (Germany) <><
http://Vir.homelinux.org/
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080508/ad80bc69/attachment.sig>
More information about the kde-core-devel
mailing list