On CYGWIN, I want a BASH script to:
- create an SSH tunnel to a remote server.
- Do some work locally that uses the tunnel.
- Then shutdown the tunnel.
The "shutdown part" has me perplexed.
Currently, I have a lame solution. In one shell I run the following to create a tunnel.
# Create the tunnel - this works! It runs forever, until shell is quit.
ssh -nNT -L 50000:localhost:3306 jm@sampledomain.com
Then, in another shell window, I do my work
# Do some MYSQL stuff over local port 50000 (which goes to remote port 3306)
Finally, when I am done. I close the first shell window to kill the tunnel.
I'd like to do this all in one script like: # Create tunnel # do work # Kill tunnel
How do I keep track of the tunnel process, so I know which one to kill?
You can tell SSH to background itself with the -f option but you won't get the PID with $!. Also instead of having your script sleep an arbitrary amount of time before you use the tunnel, you can use -o ExitOnForwardFailure=yes with -f and SSH will wait for all remote port forwards to be successfully established before placing itself in the background. You can grep the output of ps to get the PID. For example you can use
and be pretty sure you're getting the desired PID
You can do this cleanly with an ssh 'control socket'. To talk to an already-running SSH process and get it's pid, kill it etc. Use the 'control socket' (-M for master and -S for socket) as follows:
Note that my-ctrl-socket will be an actual file that is created.
I got this info from a very RTFM reply on the OpenSSH mailing list.
I prefer to launch a new shell for separate tasks and I often use the following command combination:
or sometimes:
These commands create a nested shell where I can do all my work; when I'm finished I hit CTRL-D and the parent shell cleans up and exits as well. You could easily throw
bash;
into your ssh tunnel script just before thekill
part so that when you log out of the nested shell your tunnel will be closed:ssh
to go into background with&
and not create a shell on the other side (just open the tunnel) with a command line flag (I see you already did this with-N
).PID=$!
kill $PID
EDIT: Fixed $? to $! and added the &
You could launch the
ssh
with a&
a the end, to put it in the background and grab its id when doing. Then you just have to do akill
of that id when you're done.Another potential option -- if you can install the expect package, you should be able to script the whole thing. Some good examples here: http://en.wikipedia.org/wiki/Expect