One way I can think of is to create a separate process and launch SSH in the new process.

use strict;
use warnings;

$SIG{CHLD} = "IGNORE";

my $pid = fork();
die "can not fork" if !defined $pid;
if ($pid == 0) {
  # in child process
  my $cmd = "/usr/openwin/bin/xterm -display <IPADDRESS:X.Y>";
  my $ssh = Net::SSH::Perl->new(<HOSTNAME>, port => 22);
  my $ssh->login(<USERNAME>, <PASSWORD>)
  my($out, $err) = $ssh->cmd($cmd);
  exit(0);
}

# in parent process
# carry on doing other things...

[download]

In reply to Re: Net::SSH::Perl and remote xterm by Roger
in thread Net::SSH::Perl and remote xterm by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.