Xref: utzoo comp.unix.programmer:602 comp.unix.sysv386:2607
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!psuvax1!rutgers!mcnc!duke!sam.cs.olemiss.edu!dave
From: dave@cs.olemiss.edu (David E. Johnson)
Newsgroups: comp.unix.programmer,comp.unix.sysv386
Subject: Re: sockets under ESIX Rev. D - beginner's question
Message-ID: <1990Nov30.170215.16019@cs.olemiss.edu>
Date: 30 Nov 90 17:02:15 GMT
References: <2629@wedel.hanse.de>
Organization: University of Mississippi, Dept. of Computer Science
Lines: 42

pirx@wedel.hanse.de (Jan Hinnerk Haul) writes:

>I'm at the end of my wits, so methinks I should ask the gurus...

>Just beginning to play with sockets (wanting to build a multi-machine
>chat program), I receive core dumps in listen().

>The code below is not mine; I changed only some #include directives
>(ESIX has the network stuff in /usr/include/lan) and inserted one or
>two printfs. The main() is mine, of course.

>The code belows cores in listen(). Here it goes:

....code deleted....

>Any help would be appreciated - but please do not send me long mails, I
>have to pay for them :-(

>Best regards
>Jan


The problem with the socket code you included and ESIX V is that ESIX
does not have a true socket library.  The listen() call in ESIX is
based on t_listen(), not like BSD.  Therefore, all BSD software using
sockets will _not_ work with ESIX without major changes to the socket
calls. 

The Network programmers manual for ESIX gives the definitions of the
socket library calls, but does not explain there function.

Your best off to convert the code to use the TLI functions instead of
working with their incompatible socket library.

BTW, ESIX is working on System V/R4 for production next year. That
release will have complete socket implementation.

-- 
David E. Johnson
Department of Computer Science ** Title:	Systems Programmer
The University of Mississippi  ** Telephone:	(601) 232-7396
336 Weir Hall                  ** Internet:	dave@cs.olemiss.edu