It's safer to use the list version of system:

system('/sbin/start', '/skipinfo', qq{-proxy:"$proxy_domain"});

I usually prefer to be explicit as to which executable gets called (fully qualify the path rather than a relative path). And it's a good practice to check the exit code of the system call. You'll want to read the documentation for system and perlvar (paying attention to the description of $?).

How safe all this is really depends a lot on what type of environment you're running it in. The primary advantage to using the list version of system is that it avoids the shell, thus reducing the potential for interpolation or unwanted redirection, piping, or code injection.


Dave


In reply to Re: system call windows by davido
in thread system call windows 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.