Re: Clients seeing EPIPE, dbus-daemon 1.8.16, how to debug?
Thiago Macieira <[email protected]>
| Newsgroups | gmane.comp.freedesktop.dbus |
|---|---|
| Message-ID | <5085004.zxclmjjkCa@tjmaciei-mobl4> |
On Wednesday 03 June 2015 08:07:17 Andrey Sidorov wrote:
> I've seen similar problem - https://github.com/sidorares/node-dbus/issues/82
>
> Existed in 1.8.10 and disappeared in 1.8.16
> When daemon is unhappy about serialisation being invalid I usually get
> disconnect with proper stream closing, not EPIPE
EPIPE and "proper stream closing" are just race conditions of the same
situation. EPIPE happens when you try to write(2) to the closed socket before
you read(2) from it and find out that you were disconnected.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
_______________________________________________
dbus mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dbus