I have a perl script running on HP-UX, it tars and gzips up files so I run each the commands in the background. Only trouble is the commands add spurious characters to the log file. I looked around for a day to try to fix this but no luck. here is the perl code 
foreach $tar_star_list (@tar_star_list) {
                        $complete_zip_spec = $output_path . "/" . $tar
+_star_list . ".tgz";
                        print  "\$tar_star_list $tar_star_list \n";
                        system ("tar -cvf - $tar_star_list.* | gzip > 
+$complete_zip_spec &");
                        }

[download]
and here are the spurious characters 
$tar_star_list civil
^[]0;saturnn2^G
$tar_star_list eco
^[]0;saturnn2^G
$tar_star_list slc
^[]0;saturnn2^G

[download]
saturnn2 is the hostname. How can I get rid of the ^[]0;saturnn2^G string?

In reply to system function adds spurious characters to log file 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.