Hi Guys,

Thanks for the info. To give a bit more information, I need to be able to control another daemon that operates very much like a webserver - it needs to be largely independent and needs to be persistent beyond the life of the perl script. As it's persistent, I'm fairly obviously not looking for a return value. Exec "never returns", system waits for a return value, hanging my apache, as does backticks and qx. Occasionally I even read the manuals :) Admittedly, I have not tried leaving some form of "hanging pipe", but that didn't appear to gaurantee persistence beyond the life of the script.

As for the security of the CGI script, I'm aware of taint checking and the requirements to move any user inputs away from the shell. The current problem with *that* is the deployment system is not yet fully defined (joy!). But the system security is not a *huge* issue, as the user never sees the commands being executed at the shell, and cannot enter anything anyway (not at the moment at least - when I do file uploads, the story will change).

Again, many thanks for the replies!
Mike.

PS, Got an account now :)

In reply to Re: touching off external processes within perl CGI scripts by tid
in thread touching off external processes within perl CGI scripts 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.