[lkml]   [2001]   [Feb]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: bidirectional named pipe?
    > I've countless web searches and linux-kernel archives, but I haven't yet
    > found the answer to my question.
    > I'm porting some software to Linux that requires use of a bidirectional,
    > named pipe. The architecture is as follows: A server creates a named pipe
    > in the /tmp directory. Any client can then open("/tmp/pipename",
    > O_RDWR|O_NDELAY) and gain access to the server. The pipe is bidirectional,
    > so the client and server communicate on the same pipe. I support a number
    > of clients on the single pipe using file-locking to prohibit from two
    > clients from writing/reading at once.
    > How can I do this under Linux? In SVR4 Unices, I just use pipe() as it's
    > pipes are bidirectional, and I can attach a name with fattach(). In SVR3
    > Unices, I go through a bunch of hacking using the "stream clone device --
    > /dev/spx". I experiemented with socket-based pipes under Linux, but I
    > couldn't gain access to them by open()ing the name. Is there help? I
    > really don't want to use LiS (the Linux Streams) package, as I'd rather do
    > something native and not be dependent on another module. Plus, I read
    > somewhere that this was a poor way to do things.

    How about use a unix socket instead of a named pipe.

    Lab tests show that use of micro$oft causes cancer in lab animals
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:17    [W:0.024 / U:5.140 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site