If the program takes input from STDIN and outputs to STDOUT,
the "cheap" way is to just put your program in /etc/inetd.conf,
if you are using inetd, or by using something more sophisticated
and secure like 'tcpserver' from
Dan Bernstein
a.k.a. DJB.
For a more "Perly" approach, you have to redirect both
STDIN and STDOUT to the socket:
!/usr/bin/perl
use strict;
use IO::Socket::INET;
my $sock = new IO::Socket::INET (
LocalPort => 5555,
Listen => 128,
Type => SOCK_STREAM,
Proto => 'tcp'
);
unless ($sock)
{
die "Could not create socket. Port might be in use.\n";
}
for(;;)
{
my $new_sock = $sock->accept();
if ($new_sock)
{
unless (fork())
{
$new_sock->autoflush(1);
open (STDOUT, "<&=".$new_sock->fileno());
open (STDIN, "<&=".$new_sock->fileno());
exec ("program");
}
}
}
You will note that this code has some "issues" which can
be resolved by tweaking your socket to be more like a
terminal. This, as they say, is left as an exercise for
the reader.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.