[Bugs] [Bug 1372356] glusterd experiencing repeated connect/ disconnect messages when shd is down

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1372356

Jeff Darcy <jdarcy at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jdarcy at redhat.com



--- Comment #11 from Jeff Darcy <jdarcy at redhat.com> ---
How about if we pretend that SO_ERROR doesn't exist?  (As a general rule,
something that can't be trusted might as well not exist.)  There must be some
other way we can tell whether the socket is actually connected, and generate
the correct events or state changes.  Does POLLIN|POLLERR occur in any other
cases?  Would an immediate non-blocking read give us ENOTCONN vs. EWOULDBLOCK
to distinguish these cases?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=wMigp2lQ4p&a=cc_unsubscribe