Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!motcsd!motsj1!mcdchg!ddsw1!karl
From: karl@ddsw1.MCS.COM (Karl Denninger)
Newsgroups: comp.unix.i386
Subject: Re: TCP/IP daemon quits sporadically
Summary: Change made to smail3; let's see how it works.
Message-ID: <1990Feb2.211945.683@ddsw1.MCS.COM>
Date: 2 Feb 90 21:19:45 GMT
References: <147@cms2.UUCP> <1990Jan24.185408.2157@ddsw1.MCS.COM> <28221@bigtex.cactus.org>
Reply-To: karl@mcs.MCS.COM (Karl Denninger)
Organization: Macro Computer Solutions, Inc. - Mundelein, IL
Lines: 25

In article <28221@bigtex.cactus.org> james@bigtex.cactus.org (James Van Artsdalen) writes:
>In <1990Jan24.185408.2157@ddsw1.MCS.COM>, karl@mcs.MCS.COM (Karl Denninger)
>wrote:
>
>> What >has< happened is that smail3 (sendmail replacement) will die
>> occasionally with a protocol error.  It's sitting in background, and all of
>> a sudden it stops working.  Killing and restarting it fixes the problem; I'm
>> not sure this is a 386/ix problem or one we have here locally :-)
>
>sendmail has a problem with a "protocol error" too.  The problem is
>that sometimes the socket just stops working: you can't accept any
>more connections.  The "solution" is to close the socket, and get a
>brand new one.  I suspect that this particular bug may be sendmail/tcp
>specific though - the way sendmail interacts with ISC TCP/IP results
>in memory getting clobbered (as has been pointed out, you must
>explicitly set the buffer for an fdopen()'d TCP socket).

I have made that change to smail3; I will let the net know if that takes
care of the problem or not...

--
Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl)
Public Access Data Line: [+1 708 566-8911], Voice: [+1 708 566-8910]
Macro Computer Solutions, Inc.		"Quality Solutions at a Fair Price"