[ale] Dumb Shell Scripting Question.....

[Joe Sechman]

Thanks to all....exactly what I was looking for!

-- 
Joe Sechman
Unix / Linux Systems Administrator
RLU: #367555
http://counter.li.org

On 09 Dec 2004 15:03:15 -0500, Charles Shapiro
<charles.shapiro at nubridges.com> wrote:
> Perhaps  the script(1) command is what you want. It's very handy (along
> with "set -x" for debugging shell scripts. I leave why you'd write a
> shell script long enough to require debugging as an Exercise for the
> Reader.
> 
> **
> [devel at cshapiro tmp]script /tmp/foo.out
> Script started, file is /tmp/foo.out
> bash-2.05$ echo Hey Mom!
> Hey Mom!
> bash-2.05$ uname -a
> Linux cshapiro.numethods.com 2.4.18 #5 Thu May 2 11:17:38 EDT 2002 i686
> unknown
> ^d
> bash-2.05$ Script done, file is /tmp/foo.out
> [devel at cshapiro tmp]cat /tmp/foo.out
> Script started on Thu Dec  9 15:01:06 2004
> bash-2.05$ echo Hey Mom!
> Hey Mom!
> bash-2.05$ uname -a
> Linux cshapiro.numethods.com 2.4.18 #5 Thu May 2 11:17:38 EDT 2002 i686
> unknown
> bash-2.05$
> Script done on Thu Dec  9 15:01:14 2004
> [devel at cshapiro tmp]
> **
> 
> -- CHS
> 
> 
> 
> On Thu, 2004-12-09 at 14:14, Joe Sechman wrote:
> > I was wondering if it was possible to echo the name of a running
> > command interactively in the shell to where the output contains the
> > name of the command and the resulting command output - resulting  in a
> > log of commands (w/the help of tee, etc...) that were run matched with
> > their output.