On 05/04/2013 02:08 AM, Jan Blechta wrote: > I don't anymore expect that mkfifo will work but could you sugest > somehow similiar solution?
Solution to what? > I mean the way to deal with << and >> > without drive access. I feel it is not obvious why to do it but there > is the reason. Think of these as read and write methods. Not as pipe methods. They should probably once and for all be renamed to avoid confusion. Johan > Jan > > > On Fri, 03 May 2013 16:41:45 +0200 > Johan Hake <[email protected]> wrote: >> Disclaimer: I have not used named pipes... >> >> That said, dolfin Files probably does not communicate with a bash >> pipe. Is there anything that indicates that a file sink should be >> able to communicate with a bash pipe? >> >> Johan >> >> On 05/03/2013 03:26 PM, Jan Blechta wrote: >>> Does anybody have a clue how to do something like >>> _________________ >>> File('fifo.xml') << some_dolfin_object >>> ... >>> File('fifo.xml') >> other_dolfin_object >>> _________________ >>> >>> using named pipe? If you do >>> mkfifo fifo.xml >>> in bash prior to calling python it deadlocks at <<. >>> >>> Jan >>> _______________________________________________ >>> fenics mailing list >>> [email protected] >>> http://fenicsproject.org/mailman/listinfo/fenics >>> >> >> _______________________________________________ >> fenics mailing list >> [email protected] >> http://fenicsproject.org/mailman/listinfo/fenics > _______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
