This is what I can find in the xdm-errors log of my Solaris 2.5.1 Server
running xdm, after all PC-X-Servers have been killed. (And now there are some
angry users 'peering' at me)
XIO: fatal IO error 131 (Connection reset by peer) on X server "pc-3:0.0"
xterm: fatal IO error 131 (Connection reset by peer) or KillClient on X
server "pc-6:0.0" xterm: fatal IO error 131 (Connection reset by peer) or
KillClient on X server "pc-5:0.0" XIO: fatal IO error 131 (Connection reset
by peer) on X server "pc-4:0.0" XIO: fatal IO error 131 (Connection reset by
peer) on X server "pc-5:0.0" XIO: fatal IO error 131 (Connection reset by
peer) on X server "pc-4:0.0" xterm: fatal IO error 32 (Broken pipe) or
KillClient on X server "pc-4:0.0" XIO: fatal IO error 131 (Connection reset
by peer) on X server "pc-4:0.0" xterm: fatal IO error 32 (Broken pipe) or
KillClient on X server "pc-4:0.0"
I found no documentation about this error.
What does it mean in general (who is resetting the connection) ?
What is the technical meaning of 'peer' in this context?
Is it another word for Client?
Thankx,
Erik
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/ Now offering spam-free web-based newsreading
If an X server crashes or is killed the connections
to any running clients will give this or a similar error.
The error 'Connection reset by peer' describes the condition
of the socket connection in socket/OS terms. All of this
happens underneath the X protocol. So these errors are
symptoms of the fact your X servers are being killed. At
the communication level the server and client are peers in
that they are sharing a socket connection.
>
> Thankx,
> Erik
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/ Now offering spam-free web-based newsreading
--
Chuck Dillon
c...@noran.com
--- Gratuitous waste of bandwidth omitted ---