Return to BSD News archive
#! rnews 1703 bsd Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!munnari.OZ.AU!news.hawaii.edu!ames!agate!howland.reston.ans.net!newsxfer.itd.umich.edu!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!csnews!boulder!coopnews.coop.net!news.den.mmc.com!usenet From: John Sims <sims@ipcsun3.den.mmc.com> Newsgroups: comp.unix.solaris,comp.unix.bsd Subject: Sockets Date: Thu, 16 Nov 1995 16:41:22 -0700 Organization: Lockheed Martin -- Denver InterNetNews site Lines: 18 Distribution: inet Message-ID: <30ABCC22.4A155ECE@ipcsun3.den.mmc.com> NNTP-Posting-Host: arlp001.den.mmc.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.0b2 (X11; I; Linux 1.2.13 i586) Xref: euryale.cc.adfa.oz.au comp.unix.solaris:52134 comp.unix.bsd:16753 Hi all, I have a mysterious problem with sockets under Solaris. We have ported the old bsd syslogd and its library to Solaris to try to avoid the Solaris syslogd's problem with losing so many messages. We find that if the sending program exits immediately after transmitting large numbers of messages, the last x% (generally 5 - 15%) of the messages will not be logged. This is true for all volumes of traffic. (Our test program will inject a user-specified number of messages into the syslog as fast as it can) The sending process believes it has successfully written all of the messages to the socket, but they still do not show up. If we add a one second sleep at the end of the sending process, just before it exits, all of the messages show up. Any hints, suggestions, on what is causing this? Many thanks in advance John Sims