herringtown
asked on
how do i save multiple terminal sessions that are managing remote connections as a window group??
OK, this should be really simple, but I am having trouble figuring it out. Here's my scenario -- I boot up 5 or six different terminal windows on my Mac that I then use to ssh into different servers to monitor & do some shell scripting. I have these connections saved as "Remote Connections".
What I'd like to do is "Save as a Window Group" all of my connection windows, so I can just open the Window Group at the beginning instead of running the ssh connection commands everytime. Seems like it should work, but....when you save as a window group (even when the terminal was explicity started from the remote connections menu) it just starts you up at your regular local shell -- instead of the remote connection, which was the whole point.
Really frustrating -- I expected the "Save as a Window Group" to be smart enough to save me the effort of doing "ssh -2 <user>@<IP>" in each freaking window. I may have to revert to using PuTTY on my windows machine to save myself the irritation. Please help!
What I'd like to do is "Save as a Window Group" all of my connection windows, so I can just open the Window Group at the beginning instead of running the ssh connection commands everytime. Seems like it should work, but....when you save as a window group (even when the terminal was explicity started from the remote connections menu) it just starts you up at your regular local shell -- instead of the remote connection, which was the whole point.
Really frustrating -- I expected the "Save as a Window Group" to be smart enough to save me the effort of doing "ssh -2 <user>@<IP>" in each freaking window. I may have to revert to using PuTTY on my windows machine to save myself the irritation. Please help!
ASKER
well, the thing is, I am not sure how a bash script that launches ssh sessions in the background fully addresses what I am talking about.
Bascically, I want a group of windows (which you can save in mac's terminal software) to preserve the fact that they are tied to to a remote connection. So, when I launch a window group entitled "Audiolunchbox Encoding Farm" it brings up the Mac terminal windows that I saved in that group (with display preferences) and runs the connection.
If there's a way to tie a specific connection script to a terminal window group, I'm all ears. I know you can do this with AppleScript, but I haven't ventured there yet.
But no, launching ssh sessions in the bg doesn't actually spawn separate terminal windows...at least from the terminal -- unless you WERE talking about an appleScript?
Bascically, I want a group of windows (which you can save in mac's terminal software) to preserve the fact that they are tied to to a remote connection. So, when I launch a window group entitled "Audiolunchbox Encoding Farm" it brings up the Mac terminal windows that I saved in that group (with display preferences) and runs the connection.
If there's a way to tie a specific connection script to a terminal window group, I'm all ears. I know you can do this with AppleScript, but I haven't ventured there yet.
But no, launching ssh sessions in the bg doesn't actually spawn separate terminal windows...at least from the terminal -- unless you WERE talking about an appleScript?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi herringtown, any news on this issue?
ASKER
hi there! Sorry, apparently all of my ExpertExchange emails had inexplicably been going into my spam folder, so I didn't receive any of the "new comment" notifications :( . I'm going to try your suggestion here and let you know how it goes...thanks!
ASKER
final step, saved all as a window group -- all in all, working almost as conveniently as I'd hoped..
this issue is still unsolved. I really would like a solution for this. The point is that saved window groups do not save remote connections. A irritating missing feature in terminal
ssh -2 <user>@<IP-1> &
ssh -2 <user>@<IP-2> &
ssh -2 <user>@<IP-3> &
ssh -2 <user>@<IP-4> &
ssh -2 <user>@<IP-5> &