Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:16612 comp.unix.bsd:16167 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!lll-winken.llnl.gov!taco.cc.ncsu.edu!gatech!howland.reston.ans.net!pipex!uunet!zib-berlin.de!fu-berlin.de!fub46.fddi1.fu-berlin.DE!not-for-mail From: gusw@zedat.fu-berlin.de (Gunther Schadow) Newsgroups: comp.os.386bsd.questions,comp.unix.bsd Subject: UNIX SOC_STREAM sockets don't support OOB Data??? Date: 10 Feb 1995 15:02:56 GMT Organization: Freie Universitaet Berlin Lines: 23 Message-ID: <3hfv70$slu@fu-berlin.de> NNTP-Posting-Host: fub46.fddi1.fu-berlin.de X-Access: 16 17 19 Hello, I am just a little bit disappointed: With manual pages and the PS1:8 toutorial on 4.3BSD Interprocess Communication facilities, I depended on the ability to send out of band data through a UNIX domain stream type socket inducing an SIGURG in the other process. However, now when the code is finished and in test, I experience an EOPNOTSUPP on send(..., MSG_OOB)! I reconfirmed in the kernel code and yes, uipc_userreq shows that SNDOOB is just not handled! Is there any Net/2 derived BSD that supports it? Does 4.4 BSD lite support it? How hard is it to implement that facility? I have seen that there already exists some code which is concerned with OOB data, how hard will it be to fill in the gaps? Any help is much appreciated! -Gunther Schadow -- Gunther Schadow_________________________Hopfenweg 19, Berlin 12357, FR. Germany Dept. of Anaesthesia and Operative Intensive Care Medicine/ Dept. of Medical Informatics at the |gusw@boskop.uks.fu-berlin.de Universitaetsklinikum Steglitz, Berlin, FRG. |gusw@fub46.zedat.fu-berlin.de