Re: [fuse-devel] General question hoto setup some ipc

[Stef B. <st...@gm...>]

2011/4/15 Goswin von Brederlow <gos...@we...>:
> Stef Bon <st...@gm...> writes:

>> I know and read the man page of fifo and mkfifo, I only am not
>> familiar with it. I'm posting here to get some more info that the fifo
>> is something I can use for my purpose.
>
> As pointed at above a fifo is nothing but a pipe with a name. So while a
> pipe must be inherited through a fork a fifo can just be opened by any
> process with sufficient access rights to the filesystem.
>
> I think where a fifo will fail you is that I believe the fifo will not
> give you a seperate communication channel to each instance of your
> fs. You will get race conditions on read and write and such. With pipes
> you do use a seperate pipe for each instance you fork or not?
>
I'm planning to use the fifo to make the several instances of fuse-workspace
to write to it, sending messages to the mount manager. So this
sommunications is straight forward. I've left the broadcast idea I've
spoken about earlier.

So the fifo is for the fuse-workspace's to send data to, while there
is only one app listning,
the mount manager. This will not cause any trouble I guess?? There are
more writers possible to a fifo??

Stef