Comments on: Using Bash To Output To Screen And File At The Same Time http://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/ For the betterment of the software craft... Mon, 21 Nov 2011 13:57:06 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Gopinathhttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-7077 Gopinath Tue, 05 Apr 2011 15:16:46 +0000 http://www.skorks.com/?p=1236#comment-7077 How do i transfer the temporary redirecting variable 3 to a another variable,and how does the "&-" symbol helps me . Regds Gopinath How do i transfer the temporary redirecting variable 3 to a another variable,and how does the “&-” symbol helps me .

Regds
Gopinath

]]> By: tenhttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-6093 ten Mon, 26 Jul 2010 12:35:22 +0000 http://www.skorks.com/?p=1236#comment-6093 If you still want to see stdout on screen as well, use: command ls -l file notfile 3>&2 2>&1 1>&3 3>&- | tee blah.txt See also: http://codesnippets.joyent.com/posts/show/8769 If you still want to see stdout on screen as well, use:

command ls -l file notfile 3>&2 2>&1 1>&3 3>&- | tee blah.txt

See also:

http://codesnippets.joyent.com/posts/show/8769

]]> By: Alan Skorkinhttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-3445 Alan Skorkin Sun, 31 Jan 2010 01:38:09 +0000 http://www.skorks.com/?p=1236#comment-3445 You're right, good point and a great tip, doing what you suggest works just as well, thanks for sharing. You’re right, good point and a great tip, doing what you suggest works just as well, thanks for sharing.

]]> By: Jeremy Johnstonehttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-3444 Jeremy Johnstone Sun, 31 Jan 2010 00:52:52 +0000 http://www.skorks.com/?p=1236#comment-3444 How come you don't just use: 2>&1 >/dev/null instead of pocketing stdout into a new descriptor (aka 3 above)? How come you don’t just use:

2>&1 >/dev/null

instead of pocketing stdout into a new descriptor (aka 3 above)?

]]> By: Alan Skorkinhttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-3413 Alan Skorkin Tue, 26 Jan 2010 01:39:40 +0000 http://www.skorks.com/?p=1236#comment-3413 Nothing wrong with details :) Nothing wrong with details :)

]]> By: Myleshttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-3412 Myles Mon, 25 Jan 2010 16:35:05 +0000 http://www.skorks.com/?p=1236#comment-3412 Devil/details alert. tee is a GNU-coreutils program, not a feature of bash (also part of the GNU Project, but not specifically coreutils). So the upshot is that tee will work equivalently with all shells. Devil/details alert. tee is a GNU-coreutils program, not a feature of bash (also part of the GNU Project, but not specifically coreutils). So the upshot is that tee will work equivalently with all shells.

]]> By: Alan Skorkinhttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-3385 Alan Skorkin Fri, 08 Jan 2010 10:42:33 +0000 http://www.skorks.com/?p=1236#comment-3385 Thanks mate, another good reason for me to get my act together and start posting again :). Thanks mate, another good reason for me to get my act together and start posting again :).

]]> By: Thomas Suttonhttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-3381 Thomas Sutton Fri, 08 Jan 2010 08:17:29 +0000 http://www.skorks.com/?p=1236#comment-3381 Nice article! I'm subscribing to your RSS feed. Do note though that redirecting file descriptors as you've described is specified in <a href="http://www.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_07" rel="nofollow">section 2.7 of volume 3</a> of the <a href="http://www.opengroup.org/onlinepubs/9699919799/" rel="nofollow">POSIX:2008/IEEE Std 1003.1-2008</a> standard. Anything that calls itself <code>/bin/sh</code> -- often bash on GNU/Linux systems -- should definitely do this! Thanks. Nice article! I’m subscribing to your RSS feed.

Do note though that redirecting file descriptors as you’ve described is specified in section 2.7 of volume 3 of the POSIX:2008/IEEE Std 1003.1-2008 standard. Anything that calls itself /bin/sh — often bash on GNU/Linux systems — should definitely do this!

Thanks.

]]> By: Tim Whitehttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-3334 Tim White Sun, 15 Nov 2009 23:25:09 +0000 http://www.skorks.com/?p=1236#comment-3334 Nice technique for separating stdout and stderr. That may come in handy with a bash function library I wrote for displaying nicely formatted output messages: <a href="http://www.zulius.com/freebies/bash-beauty-output-for-bash-scripts/" rel="nofollow">http://www.zulius.com/freebies/bash-beauty-output-for-bash-scripts/</a> Nice technique for separating stdout and stderr. That may come in handy with a bash function library I wrote for displaying nicely formatted output messages:

http://www.zulius.com/freebies/bash-beauty-output-for-bash-scripts/

]]> By: Alan Skorkinhttp://www.skorks.com/2009/09/using-bash-to-output-to-screen-and-file-at-the-same-time/comment-page-1/#comment-3139 Alan Skorkin Fri, 02 Oct 2009 02:38:46 +0000 http://www.skorks.com/?p=1236#comment-3139 Well, you're right tee will work on any *nix, however, there was more to the post than just noting the existence of tee. The rest was all about redirection and file descriptors, and these will not necessarily work the same with every shell on any *nix. I am working with bash, and I try to write the post in such a way that I know everything I say will work for sure, therefore I specify bash. Of course if the stuff in a post happens to work in a different shell or on a different OS that's just a bonus :). Well, you’re right tee will work on any *nix, however, there was more to the post than just noting the existence of tee. The rest was all about redirection and file descriptors, and these will not necessarily work the same with every shell on any *nix.

I am working with bash, and I try to write the post in such a way that I know everything I say will work for sure, therefore I specify bash. Of course if the stuff in a post happens to work in a different shell or on a different OS that’s just a bonus :).

]]>