Thank you very much for the reply zentara, I think you're exactly right.
Unfortunately my reader/writer need to know what each other are doing :) because I write a value and the device hanging off the port is then expected to send me data. Currently my reading portion only expects data when it "knows" that the writing has happened. After your advice I tackled the problem from the outside. I made a named pipe, and then just ran a simple background process
cat /dev/mydevice > /dir/my_named_pipe
My writing portion opens /dev/mydevice and writes there, but the reader portion then reads from /dir/my_named_pipe. Seems to work pretty well as the pipe hangs onto the data until someone actually comes along to read it. I tried opening /dev/mydevice with pipes in the open call, but it just didn't work, this does though.
Thanks again for the help.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||