There is a neat program called ser2net that would allow you to maintain these things as two separate programs. Basically, it would expose the serial port via a tcp socket that program #1 can connect to, and is able to talk bidirectionally just like any socket client.
The second program...the one that just needs read access to what's coming out of the port could do one of two things:
- Continuously watch the output of a "tracefile" that ser2net can provide
- Or, it can also connect (via tcp) to a separate control port, provided by ser2net, send the string "monitor term <port>", and then it will get a streamed copy of everything coming from the serial port.
It does support binding it's listen ports to only localhost, so it doesn't need to expose all of this to outside hosts.
The man page is here
. Prebuilt packages are out there for debian, redhat, etc.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||