Thanks, The "tee" command seemed to do the trick. Didn't have any problem with with the stdin or stdout. It made a really nice log file for me during a scripted Debian install.
Now if I could just solve a few X windows problems. I need an Xaw library that has decent scroll bars (the libXaw7 widgets seem to be pretty lame...still). Also, my primary blue is too light by a couple shades. Only in X, not on a console tty. - Craig ----- Original Message ----- From: "James Washer" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Saturday, January 22, 2005 9:27 PM Subject: Re: [RLUG] Question Though it does affect the output... namely because the first command no longer sees its standard output going to a terminal device, so it tends to buffer to block boundaries. If you want to avoid that behaviour, you'll have to write a small little utility that will establish a pseudo tty for the first command to write to. - jim On Sat, 22 Jan 2005 12:46:12 -0800 Brian Chrisman <[EMAIL PROTECTED]> wrote: > On Sat, Jan 22, 2005 at 12:30:33PM -0800, Craig H. Block wrote: > > I remember on SCO Unix there was a way to copy stdout to a file without > > affecting output to the screen. Is there a way to do that with Linux? > > (not ">some_file 2>&1" which diverts instead of copies). > > cmd 2>&1 | tee (filename) > should work... > > > > > Thanks, > > > > - Craig > > > > > > _______________________________________________ > > RLUG mailing list > > [email protected] > > http://lists.rlug.org/mailman/listinfo/rlug > > _______________________________________________ > RLUG mailing list > [email protected] > http://lists.rlug.org/mailman/listinfo/rlug > _______________________________________________ RLUG mailing list [email protected] http://lists.rlug.org/mailman/listinfo/rlug _______________________________________________ RLUG mailing list [email protected] http://lists.rlug.org/mailman/listinfo/rlug
