Path: utzoo!attcan!uunet!wuarchive!swbatl!texbell!fdata.UUCP!tore
From: tore%fdata.UUCP@nac.no (Tore Ingholm)
Newsgroups: comp.sys.ncr
Subject: WIN/TCP - socket descriptor problem
Message-ID: <483@texbell.sbc.com>
Date: 14 Sep 90 15:00:05 GMT
Organization: Fellesdata AS, Oslo, Norway
Lines: 23
Resender: towers@texbell.sbc.com (NCR Tower Mailing List)

Hi,

In order to port an existing Towernet communication package to
a 32/700 with WIN/TCP using the socket interface, following problem
occurs:

I have a process allocating a Tcp/Ip socket and binding it to a well-
known port, then the program forks another process which makes an execl()
to overlay a new program. A call to accept() on the described socket in
the new process results in error: EOPNOTSUPP, which according to the
manual means: The referenced socket is not of type SOCK_STREAM.

The problem occurs only in the Tcp/Ip version, not for Towernet.

Is this a bug in WIN/TCP or is the socket descriptor not inherited by the
new program after an execl() call, (file descriptors are, according to the
manual), or do you have other suggestions?

-- 
     Tore Ingholm                        mail: mcsun!nuug!fdata!tore    
     Fellesdata AS 			       (or) tore%fdata.UUCP@nac.no
     Box 248 Skoeyen, 			 tel:  +47-2 ( 52-86-13 / 52-80-80 )
     N-0212 OSLO 2, NORWAY 		 fax:  +47 2 52 85 10