#!/usr/bin/perl -w # detach from the terminal, go into the BG and then exec a program # detacher.pl <program> {parm1} {parm2} ... use strict; sub main { my ($pid,$line); my (@args); # fork and exit if parent $pid = fork; if($pid) { exit 0; } # duplicate STD paths open (DUPOUT,">&STDOUT"); open (DUPERR,">&STDERR"); open (DUPIN, "<&STDIN"); # close STD paths so parent can exit clenaly close STDOUT; close STDERR; close STDIN; # restore the STD paths from duplicates open (STDOUT,">&DUPOUT"); open (STDERR,">&DUPERR"); open (STDIN,"<&DUPIN"); # avoid leaks! close teh duplicate paths close DUPOUT; close DUPERR; close DUPIN; # construct a command list @args = (); foreach $line (@ARGV) { push @args,$line; } # finally exec the new program exec @args; } main()

In reply to detacher.pl by enemyofthestate

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.