The trick is to keep track of the PID as you launch the process. On non-Windows systems, this is easiest done through the magic of exec, which replaces the current process by the other process, keeping the PID ($$) the same. So you can store $$ and then exec the "real" process:

sub launch { my ($pid_file,@process_and_args) = @_; open my $fh, '>', $pid_file # or print to STDOUT for easier handli +ng by ssh? or die "Couldn't create '$pid_file': $!"; print {$fh} $$; exec(@process_and_args) or die "Couldn't launch [@process_and_args]: $!"; };

You have to decide whether to output the PID to a file or to directly output it to STDOUT and read it from your ssh launcher and store it in the controlling master.


In reply to Re: how to kill deattached process by Corion
in thread how to kill deattached process by baxy77bax

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.