Return to BSD News archive
Xref: sserve comp.unix.questions:51197 comp.unix.bsd:14252
Newsgroups: comp.unix.questions,comp.unix.bsd
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!sgiblab!sdd.hp.com!math.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!howland.reston.ans.net!EU.net!sunic!trane.uninett.no!nac.no!nntp.nta.no!itoe-02!tm3an
From: tm3an@itoe-02.uucp (Arnar Nesset)
Subject: Re: (Q) BSD sockets - how to handle properly
Message-ID: <1994Jun29.101043.16437@nntp.nta.no>
Keywords: socket, IPC
Sender: news@nntp.nta.no
Nntp-Posting-Host: 148.122.1.48
Organization: Norwegian Telecom, IT dept., Lillehammer
References: <1994Jun27.132141.19137@nntp.nta.no>
Date: Wed, 29 Jun 94 10:10:43 GMT
Lines: 18
This is a summary of the replies I got to my previous article on how to
deal with sockets properly in a simple program problem.
Semaphores was suggested by one, and probably does the business, I didn't
try it.
I seemed to be right in assuming that sockets was the way to go. I received
pointers to things to be aware of as a newbie to sockets - thanks. And I
was assured that I did nothing wrong in not forking off child processes to
handle request from clients, as I had a very simple task, really.
Cheers all,
--
--
(o) (o) Arnar
-----oOO--(_)--OOo---------------------------------------------------
arnar.nesset@ti-lillehammer.televerket.tele.no