🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.bugs.4bsd
Article #174

no EOF for stream unix socket reader

#174
From: Jong Kim
Date: Thu, 19 Jul 1990 02:55
18 lines
959 bytes
With a stream unix socket, shouldn't the PRU_SHUTDOWN case in uipc_usrreq.c
call socantrecvmore for the receiver's socket? Currently the receiver
is not notified if the writer calls shutdown(how = 1). The following
change in uipc_usrreq.c will cause the receiver to get EOF after reading
all remaining data.


unp_usrclosed(unp)
        struct unpcb *unp;
{
        struct socket *so;
        if (!unp || unp->unp_inode || !unp->unp_conn)
                return;
        if ((so = unp->unp_conn->unp_socket) != NULL)
                socantrcvmore(so);
}

\jong
Technical Details
Message-ID: <64508@sgi.sgi.com>
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!wuarchive!rex!ames!sgi!jong@dizzy.wpd.sgi.com

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!wuarchive!rex!ames!sgi!jong@dizzy.wpd.sgi.com
From: jong@dizzy.wpd.sgi.com (Jong Kim)
Newsgroups: comp.bugs.4bsd
Subject: no EOF for stream unix socket reader
Keywords: Bug or Feature?
Message-ID: <64508@sgi.sgi.com>
Date: 19 Jul 90 02:55:18 GMT
Sender: jong@dizzy.wpd.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 18