Hey Ladies/Gents.
This follows the other thread i posted over the last few weeks on
devOPS stuff for managing groups of remote droplets/vms.
My approach for now to implement clusterSSH as well as screen to be
able to auto gen the remote droplets, and to be able to ssh into them
to view status, as well as to track progress, and run remote processes
with the screen env.
I'm currently testing the screen function to get more familiar with
it, and running into an issue.
I generate a basic test screen session, with a name. This session is there.
screen -ls
shows the session and i can pop another term, and ssh into the box,,
and attach to the screen session
screen -r 'testname' gets into the session.
However, when I attempt to do a simple test, to run a remote cmd
within the remote ssh/screen env, I run into issues. I get an error in
that the ssh/screen/cmd needs a terminal
-----Must be connected to a terminal.
Ive tested/tried a few different iterations of the ssh/screen/ls to
try to get this to work.
//--this actually generates the screen sesstion on the remote box, no issues
ssh crawl_user@192.81.214.49 "screen -d -m -S 'testname' "
//--which of these (or something else) to remotely run ls in the
ssh/screen session??
--which of these??
ssh crawl_user@192.81.214.49 'screen -m -d -r "testname" "ls" '
ssh crawl_user@192.81.214.49 'screen -r "testname" "ls" '
ssh -t crawl_user@192.81.214.49 'screen -r "testname" "nhup ls &" '
--- this almost seems to work, but the process hangs, leaving the
user in the remote term, in other words, it doesn't run, and return to
the calling term
I've been looking at the net/goog/SO/etc.. but no real insight yet..
Thoughts/comments appreciated...
Thanks
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
