Hello,
I am still having problem accessing one of my FIFOs.
This FIFO was created by a real-time module, and it is write-only.
Now, another real-time module is accessing it and tries to write to it.
I get "Can't send a command to Real-time task" error no matter what I do.
What makes me curious that I can access the same FIFO from a user
program no problem.
I know that FIFOs are pipes, and they have identifiers that should be
accessible to any module that __did_not__open this particular FIFO ?
Otherwise, how do I make sure that the FIFO that I am trying to access is
not "tied up" by another module that has created it and may be using it ?
Do I need to lock out critical sections so no 2 accesses are done
simutaneously on the same FIFO or rt linux has a lock already ?
Sincerely,
Olga
______________________________________________________________________
Olga Mill ([EMAIL PROTECTED])
Eastern Washington University
Voice Mail : (509) 359-6907
__________________________________________________________________________
-- [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/
