|
Home > Archive > Unix administration > February 2005 > unix riddlee
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| puzzlecracker 2005-02-21, 6:00 pm |
| Say that when you run the Unix command junky in your shell, it spits
out a ton of text to the console, too much for your console buffer to
hold. How would you run it so that you can look at everything it
outputs after it finishes?
| |
| Barry Margolin 2005-02-21, 6:00 pm |
| In article <1109019597.399243.74360@z14g2000cwz.googlegroups.com>,
"puzzlecracker" <ironsel2000@gmail.com> wrote:
> Say that when you run the Unix command junky in your shell, it spits
> out a ton of text to the console, too much for your console buffer to
> hold. How would you run it so that you can look at everything it
> outputs after it finishes?
junky | less
will pipe the output to a pager, that lets you read it slowly. If your
system doesn't have "less", it probably has its predecessary "more".
Or:
junky > filename
and then read filename in an editor.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
| |
| Bill Marcum 2005-02-22, 5:53 pm |
| On 21 Feb 2005 13:07:53 -0800, puzzlecracker
<ironsel2000@gmail.com> wrote:
> Say that when you run the Unix command junky in your shell, it spits
> out a ton of text to the console, too much for your console buffer to
> hold. How would you run it so that you can look at everything it
> outputs after it finishes?
>
command | less
| |
| John Kelly 2005-02-22, 5:53 pm |
| puzzlecracker wrote:
> Say that when you run the Unix command junky in your shell, it spits
> out a ton of text to the console, too much for your console buffer to
> hold. How would you run it so that you can look at everything it
> outputs after it finishes?
>
command 2>&1 | more
|
|
|
|
|