dbus: timeout behavior

[dperpeet]

The daemon behavior seems inconsistent with what can usually be expected. If Cockpit doesn't explicitly call "start", the daemon seems to drop connections.

I would expect that once a dbus connection is opened, information can be queried and the daemon takes care of its internal state.

[dperpeet]

It's worth noting that I'm not sure what happens with the "start"ed daemon when Cockpit exits. It stays around for a while, but I don't know if forever or until some (long) timeout.