Wonderful! Thanks a lot. That makes sense and I just got it to work. Cleaning up is a bit more involved now, but that's working now as well.
Before I found out about this mailing list I posted a question on Stackoverflow ([1]http://stackoverflow.com/questions/26791920/named-pipes-and-aufs-issues) . If you have an account there, you might want to copy your reply there, otherwise I'll do it in a few days - obviously crediting you. Thanks again for the prompt and helpful answer. Cheers, -max On Fri Nov 07 2014 at 1:06:36 PM <[2]sf...@users.sourceforge.net> wrote: Hello Max, Max Ott: > If I write and read to the same fifo path (e.g a/fifo) everything > works fine, but if I do > > shell1$ cat a/fifo > ... > shell2$ echo 'hi' > b/fifo > > nothing happens. Because your 'a' and 'b' are different mount from each other, and 'a/fifo' and 'b/fifo' are different entries. Try stat(2) against these two fifos and you will see different st_dev. As you might know, when you try communicating via fifo, you need to operate on the same/identical fifo. Here 'identical' means that both of st_dev and st_ino should match. Aufs has different st_dev per mount and the inode numbers are managed per mount. As long as you use different mount, you cannot communicate. But you can escape from aufs by 'bind' mounting. $ sudo mount -o bind common/fifo a/fifo $ sudo mount -o bind common/fifo b/fifo Try stat(2) again and confirm it. J. R. Okajima References 1. http://stackoverflow.com/questions/26791920/named-pipes-and-aufs-issues 2. mailto:sf...@users.sourceforge.net
------------------------------------------------------------------------------
