Issue with _dbus_write_socket on windows

Peter Kümmel syntheticpp at
Sun Nov 19 10:22:51 PST 2006

Havoc Pennington wrote:
> Christian Ehrlicher wrote:
>> Havoc Pennington schrieb:
>>> Christian Ehrlicher wrote:
>>>> Thx, for the hints. Now the daemon is started on demand and adress is
>>>> read from shared memory.
>>> How did you go about making it per-user instead of per-machine?
>> Currently this is not supported, but I think it should be possible by
>> adding a userid or something else to the shm name.
> My .02, I don't think this is a "would be nice" feature - it's pretty
> essential to dbus working right.

We now append the uid to our global locks.

>> But the bigger
>> problem is - how can I avoid using the same port twice? And how can I
>> react when the port is already in use?
> I already mentioned that in another mail - you may need to write a new
> DBusTransport variant that uses named pipes or Windows messages. That
> would be cleaner and faster anyway. Or figure out how to define the TCP
> stuff, I'm not sure how the X server defines it if there are multiple X
> servers, but it could work in the same way perhaps.

and we could get a free port from the os. :)

> Havoc
> _______________________________________________
> dbus mailing list
> dbus at

Peter Kümmel

More information about the dbus mailing list