hola,
i have an application written for x windows that accesses FIFOs to
communicate with a rt task. I created a multithreaded app where the
only worker (child) pthread waits for data from the FIFO, while the boss
(parent) pthread continues on in the application. I'm using the linux
command 'read' to access the FIFO. The documentation states that read
will block on FIFO access if no data is present, which is the behavior
that i'm seeing, although the blocking seems to be occuring with the
entire process (application) and not the single thread. I know this
because I can open the FIFO as nonblocking and the reading thread spins
waiting for data, while opening the FIFO in as blocking causes the
process to stall. The documenation I've found for 'read' is
confusing... going back and forth between talking about blocking of
processes and threads....
So, my question is... am i doing something drastically wrong, or should
i look for another way of implementing this functionality (i.e. reading
of the FIFO only when data is present and letting the app do what it
needs to in the meantime)
thanks,
brent
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
