On Thu, 2006-02-23 at 10:16 -0500, Robert Love wrote:
I think we can separate should never restart the system bus from foo
should be able to survive a system bus restart.
The former is good policy, the latter is good programming. We can have
both.
Well, half right anyway. The former
On Thu, 2006-02-23 at 10:16 -0500, Robert Love wrote:
On Fri, 2006-02-17 at 12:16 -0500, Dan Williams wrote:
There have been quite a few discussions about this sort of thing, and
the general conclusion has been don't do that...
That was the consensus of some, awhile back, but I do not
On Fri, 2006-02-17 at 12:16 -0500, Dan Williams wrote:
There have been quite a few discussions about this sort of thing, and
the general conclusion has been don't do that...
That was the consensus of some, awhile back, but I do not think anyone
is singing that song anymore. Many DBUS-using
Robert Love wrote:
I think we can separate should never restart the system bus from foo
should be able to survive a system bus restart.
The former is good policy, the latter is good programming. We can have
both.
Brilliantly concise :-)
When one considers this a stability issue and not a
Hi,
Currently NetworkManager does not recover once the D-BUS system bus is
restarted. With the attached patch it will survive such a exceptional
conditions.
It does the following:
* add function nm_dbus_reinit to src/NetworkManagerDbus.c.
* fix: handle the signal Disconnected on
On Fri, 2006-02-17 at 17:52 +0100, Timo Hoenig wrote:
Hi,
Currently NetworkManager does not recover once the D-BUS system bus is
restarted. With the attached patch it will survive such a exceptional
conditions.
It does the following:
* add function nm_dbus_reinit to