My immediate thought was '&' and signals. Following any command in Linux with an ampersand will cause it to run in the background (much like the bg command). The signals will allow you to control the script without having an interactive interface to it. As a comprehensive solution:

  • Create 2 scripts, we'll say the first is called jdataserver.pl, and the second is jdatalisten.pl
  • Have jdataserver.pl check for command-line options. If none are given, have it exec() jdatalisten.pl in the background (using bg or &, or is there a function in Perl?)
  • If the -i command-line option is given, have it check to see if jdatalisten.pl is running and if so send it a signal (there are user-defined ones on most OSes) that it knows how to catch.
  • If the -k command-line option is given, have it check to see if jdatalisten.pl is running and if so send it a SIGINT, SIGKILL, SIGQUIT, or whatever signal for it to catch.
  • Continue as desired for other functionality.

    This could possibly also be accomplished with a single script, just having it check for its own existence in the processes (although it would have to exclude its own pid). [id://roger] also had some good resources posted above.


    In reply to Re: making a perl script TSR? (on linux) by wink
    in thread making a perl script TSR? (on linux) 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.