Issue with _dbus_write_socket on windows

Ralf Habacker ralf.habacker at
Tue Nov 21 06:45:16 PST 2006

Havoc Pennington schrieb:
> Hi,
> Looking at the code you guys have in svn, it seems like the big
> question is how the session bus gets started. On unix, we have two
> answers:
>  - normally, the session bus is started by X init scripts and then
>    located with an environment variable
>  - as a fallback, the bus can be autolaunched and then have its address
>    stored in a file in the home directory that is
>    per-machine-per-X-display
> On Windows, I think just one answer is probably fine:
>  - the bus is always autolaunched, and only one instance of
>    it exists at a time (using whatever mechanism tbd)
Have you thought about accessing a dbus-daemon on a given windows pc
from another unix or windows pc ?
How should it be able if the daemon is autolaunched ? Or is this such a
use case only limited to the system bus, which should have a well known
tcp port ?


More information about the dbus mailing list