Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!hp4nl!philmds!phcoms!gordon
From: gordon@phcoms.philips.nl (Colin Gordon)
Newsgroups: comp.protocols.tcp-ip
Subject: problems using inet daemon
Message-ID: <359@phcoms.philips.nl>
Date: 5 Apr 89 17:12:53 GMT
Reply-To: gordon@phcoms.philips.nl (Colin Gordon)
Organization: Philips Components - SERI, Eindhoven, The Netherlands
Lines: 15

I have a TCP client/server type application which I'm trying to start
from the inetd daemon. I can get the client to connect to my
server machine ok. The inetd daemon passes the connection to my
program as file descriptor 0 ok. I can then shutdown stdout & stderr
and dup them to 0 and succesfully write back to the client.

I can't however do any reads from stdin, which I assume is the
socket connection. The write/send from the client end seem to
be ok.

Does anybody have any idea where I'm going wrong ?
-- 
Colin Gordon, Philips Components, Eindhoven, The Netherlands
Tel: +31-40-723149	Fax: +31-40-723846
UUCP: 	..!mcvax!philmds!phcoms!gordon	gordon@phcoms.philips.nl