qx acts like a double-quoted (interpolated) string, so you need to escape stuff, i.e. 

my $dbpass=qx{ password_decode \$(grep "name=\\"db\\"" /opt/SecureSphe
+re/etc/bootstrap.xml|cut -d\\" -f4) };

[download]

(untested)

Alternatively, declare your command using a non-interpolating quoting mechanism, and then pass it to qx{}: 

my $cmd = q{ password_decode $(grep "name=\"db\"" /opt/SecureSphere/et
+c/bootstrap.xml|cut -d\" -f4) };
my $dbpass = qx{ $cmd };

[download]

Hint: replace qx{} with qq{} and print it, and you'll see what the shell sees with your version, e.g. 

password_decode 999 101 104 814 999 1035 1070grep "name="db"" /opt/Sec
+ureSphere/etc/bootstrap.xml|cut -d" -f4)

[download]

In reply to Re: CX or System by Eliya
in thread CX or System by TCPDump

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.