Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!mentor.cc.purdue.edu!yuf
From: yuf@mentor.cc.purdue.edu (Kyle Grieser)
Newsgroups: comp.unix.wizards
Subject: Re: Named pipes?
Keywords: interprocess communication
Message-ID: <2491@mentor.cc.purdue.edu>
Date: 20 Apr 89 18:44:51 GMT
References: <704@sdrc.UUCP> <5367@cs.Buffalo.EDU>
Reply-To: yuf@mentor.cc.purdue.edu (Kyle Grieser)
Organization: PUCC UNIX Group
Lines: 21

In article <5367@cs.Buffalo.EDU> ugkamins@sunybcs.UUCP (John Kaminski) writes:
>In article <704@sdrc.UUCP> scwilk@sdrc.UUCP (Ken_Wilkinson) writes:
>>
>>     I am to impliment IPC's for a product.  However, message queues
>> "may" not do the job for me.  It was mentioned that "named pipes"
>> could be a solution.  Does anyone have a suggestion for sources
>> which would document named pipes? Also sample code fragments would
>> be helpful too. 
>
>Most of the docs I can find on named pipes are in mknod(2).

	Yes, from my experience with named pipes there isn't much out
there to help you out.  mknod(2) is the only place that I could find
any information.  The best way to learn them is to play with them.
As long as you remember that they are FIFOs it is quite easy to see
how they behave.  Readers will block if there is nothing to read, and
writers will block if there is no one reading from the other end.

-----
Kyle Grieser, Purdue University Computing Center
mentor.cc.purdue.edu!yuf, yuf@mentor.cc.purdue.edu