Just for the record, here's the final code from the actual script it's being used in, which works correctly. This subroutine forks off an external command and returns a filehandle that you can read and write to, and convinces the external program that it's running in a terminal.
use IO::Handle;
use IO::Pty;
use POSIX;
sub forkptycmd($) {
my $cmd = shift;
my $pty = new IO::Pty;
my $pid = fork;
if(!defined($pid)) { die "error forking: $!"; }
if($pid==0) {
POSIX::setsid();
my $slave = $pty->slave;
close($pty);
STDOUT->fdopen($slave,'>') || die $!;
STDIN->fdopen($slave,'<') || die $!;
STDERR->fdopen(\*STDOUT,'>') || die $!;
close($slave);
exec($cmd);
}
$pty->close_slave();
return $pty;
}
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|