ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have been searching for hours and hours but I cant find the answer to this problem.
I have a simple pipeline that reads:
command1 | command2 | tee /dev/tty | command3
The problem is the when 'tee /dev/tty' displays the output to my terminal there is so much data that it goes off the screen. I have tried redirecting to 'more' and 'less' but that does not work.
Is there anyway to page the output of 'tee /dev/tty' ?
You rule! That worked like a charm Now I am going to up on the syntax you used. (I do not understand why this command does not work with a | to the last command instead of ; )
Thanks again for such a great responce to my first post.
I'm pretty much a n00b myself (even tho i've been using *nix for a few years LOL) but you could send the output of tee to a file, allowing you to read it at a later date:
Redirecting the 'tee' output to a file to read later is a good idea too. But in this case I wanted to use 'tee /dev/tty' to check the output of part of my pipe as the pipeline ran. (Plus I needed to learn how to page the output of 'tty' for a class I'm taking)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.