I have a script that writes output to a file using redirection:

exec &> $TEMPFILE

It would be useful if I also had the option to display the information so I was wondering how one might go about that from within a script?

Tried this but doesn't seem to work:

exec &> | tee $TEMPFILE


Jim c.

echo "---- mounting backup device hda10 --" | tee -a $SUMM $LOG

The above is a line from one of my backup scripts. I use the `tee` tool to make the output echo to the screen, as well as to the $SUMM and $LOG files.

Notice that there is no &> in the expression. Perhaps you could post the exact chunk of code you're working on, in case I'm missing something here, but otherwise, try just piping the `exec` directly via the pipe, into `tee` as I have done.

Sasha

I could do it that way but then I would have to do that for each command that the script uses for output. My objective is to turn it on once and then turn it off later. Currently what is being used is

exec &> $TEMPFILE

Which redirects standard out and standard error to a file until later in the script where it is turned off with

exec 1> /dev/tty
exec 2> /dev/tty

Perhaps what I need is a named pipe or something.

As far as I know, there is no chance to redirect standard output and standard error to a file and display them simultaneously using just a single exec statement. The process is a little more complicate and involves named pipes. Instead of adventuring in a long explanation, I prefer to point you to this article where the process is explained in detail, step by step.

@GrapefruiTgirl: I assume the OP wants to use "exec >" to redirect the standard output of the whole script without piping to tee every command in the script itself. Nevertheless your advice is good and I use the same quite often in my work.

Cheers!
Alex

Just seen your new post. The answer is yes and you will find the article I linked really useful.

Yes, I think I understand now, and have another suggestion or two, which again may be "not precisely" what the OP wants, but may work nonetheless. (I haven't read the link provided by colucix, so it may well provide exactly what you want).

1) Look into the `set` command. I believe `set` can be used to set aspects of bash, or things running within bash, including re/direction for the duration of a script or bash instance.

2) Put all the code that you want re/redirected, into ONE script, and then, execute THAT script with ./script | tee 2&>1

3) put your stuff that you want re/directed, into a FUNCTION, or between { } braces, and subsequently re/direct the function call or {braced code} into the `tee` command.

Anyhow, these are just ideas, which work for me in various circumstances, but again, might not do precisely what you want, in your specific case.

If the link provided by colucix does give the answer you need, please enlighten us, so we'll (or for myself anyhow) know in the future

EDIT -- new posts above/below -- hopefully you get the named pipe to do what you want; please show us how, when you get it sorted!

Regards,
Sasha