Shell Programming and Scripting

Hi Methyl, it does not start a new shell, see: exec: description

Maybe if you could tell us what exactly you are trying to do in your script, we might come up with a few suggestions.

Interaction of the shell with Oracle doesn't have to be complicated. But you got to help us help you here.

tyler_durden

@Scrutinizer
Thanks.
Never found a use for " exec > $LOGFILE 2>&1 " but I see from the link you post how it might work but I cannot match the syntax used by the O/P with any of the examples.
We use "exec" to lock people into a shell menu (which does start a new shell). Any lines in the calling script below the "exec" line are never executed and the "drop-through" in the exec'd shell menu logs you out. That's what I though was happening to the O/P.

I am just trying to capture all the echo comments. The script includes zipping and mailing which turnouts some system messages like below

adding: file1.csv (deflated 92%)
adding: file2.csv (deflated 46%)

redirecting to some o/p file on each single stmt may not be appropriate. I tried to simulate in simple code but again it quits the session after execution...
pls see below

Code:

user@server:/path> cat test.sh
#!/bin/bash

LOGFILE=/logpath/testlog.`date "+%y%m%d" `.$$
exec > $LOGFILE 2>&1

echo Line 1

echo Line 2

exit
user@server:/path>
user@server:/path>. test.sh

it exits from the session and need to relogin to see the log

Code:

user@server:/logpath> cat testlog.110214.3496
Line 1
Line 2
user@server:/logpath>

hope now my req is clear, appreciate for any alternate idea to get rid of this concept

Try:

Code:

chmod +x test.sh
./test.sh

You can just remove the exit statement by the way. It serves no purpose...

Thanks a lot it really works with exit stmt as well.

by the way whats difference in dot space and other one.

With dot space you are "sourcing" the commands in the script, which mean you execute them in your current environment, which is your interactive shell. The exit statement exits the shell which is your interactive shell, so your putty session gets terminated...

The other way is called executing and in this case a new shell is started in which the script is run. Once it exits, it only exits that shell and your interactive shell remains active...