script closing window

lk4772 · 11-23-2009, 02:11 PM

Hello! I'm new to this site, and trying to refresh my memory from 5 years ago since I last worked with Oracle and Unix. So please be patient with me! LOL

I have a shell script using sh that whenever I run it, it closes my Putty session! The script has only 2 lines, an echo statement and the first is the #!/bin/sh command....any help would be much appreciated! thanks!

rweaver · 11-23-2009, 02:12 PM

Can you show a copy of the script?

lk4772 · 11-23-2009, 02:14 PM

I had even commented out the echo statement and it still closes the window? here's the exact contents of the script - I wrote using the VI editor so that there shouldn't be any problems with return characters...

#!/bin/sh
#echo "starting script";

lk4772 · 11-23-2009, 02:29 PM

I also tried using the printf function instead of echo, but that closes my putty session as well....

i92guboj · 11-23-2009, 03:16 PM

*How* are you running this script? Step by step, please.

That script does actually nothing because everything is commented out. At most, it should echo a message if you uncoment the 2nd line.

lk4772 · 11-23-2009, 03:27 PM

I'm logging into putty, using the "cd" command I'm going to the directory where the script is stored, and then I'm typing in "exec <scriptname>"

I know the script isn't really doing anything, I'm just trying to get started on verifying that an easy script (like this one) will work so that I can figure out why another script is not working by adding in pieces/parts of the other script, but I don't want it to close putty all the time - don't want to keep logging back in - does that make sense?

lk4772 · 11-23-2009, 03:33 PM

I have also just tried the below script, and it worked - displayed the #1, but as soon as I put the last line in ("echo script started;") it closes the window - tried it with and without the quotes around script started....

#!/bin/sh
export LeisaNbr=0;
let "LeisaNbr = LeisaNbr + 1";
echo $LeisaNbr;
echo script started;

i92guboj · 11-23-2009, 03:37 PM

Quote:

Originally Posted by lk4772

I'm logging into putty, using the "cd" command I'm going to the directory where the script is stored, and then I'm typing in "exec <scriptname>"

That's what I wanted to hear. "exec" forks a new process, then terminates the current shell. When the script ends, there's nothing in putty, no shell, so it closes.

Quote:

I know the script isn't really doing anything, I'm just trying to get started on verifying that an easy script (like this one) will work so that I can figure out why another script is not working by adding in pieces/parts of the other script, but I don't want it to close putty all the time - don't want to keep logging back in - does that make sense?

It's not the script, simply don't use exec. Either use:

Code:

sh <scriptname>

or chmod it conveniently and run it this way:

Code:

chmod a+x <scriptname>
./<scriptname>

You only have to chmod it once, of course. After that, you can run it that way.

lk4772 · 11-23-2009, 03:39 PM

that worked!!