On Mon, 14 Mar 2005 17:56:31 -0500, Colin Walters wrote:
There's so
many complicated issues in it, and it'll be a rarely-tested code path.
Right now it's a bug that the Fedora D-BUS and NetworkManager RPM
scripts restart after a package upgrade.
You should just have to reboot, IMO.
On Mon, 2005-03-14 at 17:14 -0800, Tomislav Vujec wrote:
On Mon, 14 Mar 2005 18:22:26 -0500, Colin Walters wrote:
The system bus will be restarted on reboot, however often that happens.
For my personal system that's several times a day, as apm and acpi are
broken on my laptop.
I think
On Tue, 2005-03-15 at 09:28 -0500, Colin Walters wrote:
If you run a desktop system, you should include X and gdm in there.
Neither are restarted automatically for security updates. I'm sure
there are others too that I'm not thinking of.
I would argue that there is really no fundamental
On Tue, 2005-03-15 at 08:01 -0500, Bill Rugolsky Jr. wrote:
If it is some huge bloated behemoth that may die due to bugs, or gets
killed by the OOM-killer, etc., then apps must reliably reconnect. If
it _can_ crash, it _will_ crash, quite often for certain workloads.
Well, there's no way to
On Tue, 2005-03-15 at 08:01 -0500, Bill Rugolsky Jr. wrote:
If it is some huge bloated behemoth that may die due to bugs,
Any software can crash due to bugs. The same is true for someone
writing some hypothetical D-BUS replacement on top of netlink or
whatever.
But you might notice that the
On Tue, 2005-03-15 at 11:54 -0500, Colin Walters wrote:
The problem here is that app status also depends on different subsystem
and external system status. In the other words, can I keep my TCP
connections after the reboot.
No, but in laptop+suspend case TCP connections are often broken
On Sun, 2005-03-13 at 23:29 +0100, Tom Parker wrote:
One of the things that NM has needed for a while is the ability to
properly handle Dbus disconnects, and to reconnect sanely.
I don't think we should really try to support this. Restarting D-BUS
should be viewed like trying to live-restart
On Mon, 14 Mar 2005 14:00:50 -0500, Colin Walters wrote:
On Sun, 2005-03-13 at 23:29 +0100, Tom Parker wrote:
One of the things that NM has needed for a while is the ability to
properly handle Dbus disconnects, and to reconnect sanely.
I don't think we should really try to support this.
Colin Walters wrote:
On Sun, 2005-03-13 at 23:29 +0100, Tom Parker wrote:
One of the things that NM has needed for a while is the ability to
properly handle Dbus disconnects, and to reconnect sanely.
I don't think we should really try to support this. Restarting D-BUS
should be viewed like
On Tue, 2005-03-15 at 00:27 +0200, Paul Ionescu wrote:
On Mon, 14 Mar 2005 14:00:50 -0500, Colin Walters wrote:
On Sun, 2005-03-13 at 23:29 +0100, Tom Parker wrote:
One of the things that NM has needed for a while is the ability to
properly handle Dbus disconnects, and to reconnect
[ CC'ing dbus list as this discussion is important for writers of D-BUS
applications and for packagers ]
On Mon, 2005-03-14 at 23:49 +0100, Tom Parker wrote:
I'd disagree. Yes, it'll be a pain in the ass to get right, and yup this
ain't exactly going to be the most tested code path.
I'm
On Mon, 14 Mar 2005 18:22:26 -0500, Colin Walters wrote:
The system bus will be restarted on reboot, however often that happens.
For my personal system that's several times a day, as apm and acpi are
broken on my laptop.
I think that the fact that acpi is broken on your laptop should be
12 matches
Mail list logo
