Sorry guys, but the problem is that top prints the page without the line for the CPU states, leaving that line blank. Then it has to do screen cursor positioning to update that line in realtime. But the first time it tries, it discovers that that the pipe to which you are directing output cannot accept ANSI escape sequences (needed to position the cursor) so it exits before that point.

Piping to tee doesn't work either because then tee has access to the screen device but top still hasn't got it and exits just as quickly leaving tee to duplicate the same problem.

Update: Perhaps something like Test::Expect will be able to emulate an ANSI terminal to top's satisfaction.

One world, one people


In reply to Re: Obtaining data from the top command via a pipe by anonymized user 468275
in thread Obtaining data from the top command via a pipe by tc1364

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.