Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!zombie.ncsc.mil!nntp.coast.net!chi-news.cic.net!newsjunkie.ans.net!istar.net!news1.ottawa.istar.net!fonorola!news.ottawa.istar.net!milkyway.com!not-for-mail From: mcr@metis.milkyway.com (Michael Richardson) Newsgroups: comp.unix.bsd.misc Subject: Anyone done SOCK_RDM for Unix domain? Date: 1 Jan 1996 15:09:09 -0500 Organization: Milkyway Networks Corporation, Ottawa, ON Lines: 31 Message-ID: <4c9f15$i7b@metis.milkyway.com> NNTP-Posting-Host: metis.milkyway.com It has come to a someone unantipated shock that using Unix domain sockets for syslog(3) logging isn't reliable. Oops, SOCK_DGRAM (/dev/log) doesn't guarantee delivery. BSD4.4-lite says: /* * Unix communications domain. * * TODO: * SEQPACKET, RDM * rethink name space problems * need a proper out-of-band */ at the top of kern/uipc_usrreq.c. Has anyone done RDM sockets? It would be trivial for me to modify my entire system to listen on a SOCK_RDM. Alternately, I could change the behaviour of Unix domain SOCK_DGRAM sockets to block on writes if there is no space. The problem is that on a very busy system, the syslogd may not get scheduled often enough to keep its socket queue empty. (Yes, we have bumped the hiwater mark up, but that won't eliminate the problem, just reduce the frequency of loosing log lines) I don't want to teach syslogd about SOCK_STREAM! Assuming someone done SOCK_RDM, might you have done it for StunOS as well as 4.4? (I'm using BSD/OS actually) -- :!mcr!: | <A HREF="http://www.milkyway.com/">Milkyway Networks Corporation</A> Michael Richardson | Makers of the Black Hole firewall NCF: aa714 || xx714 | +1 613 566-4574 ... mcr@milkyway.com Home: <A HREF="http://www.sandelman.ocunix.on.ca/People/Michael_Richardson/Bio.html">mcr@sandelman.ocunix.on.ca</A>. PGP key available.