Hi.. again...
ok..
If I create /etc/clusters
cat /etc/clusters
#clusters = testcluster
testcluster1 -a "-t screen -r cSession" cuser@1.2.3.4
cssh testcluster1 doesn't work... throws up a number of windows/terms
that immediately crash..
However, running
testcluster1 -a "-t screen -r cSession" cuser@1.2.3.4
from the cmdline does work...
and it displays the term/window in the running screen session..
So, got 2 questions/issues...
1- is there a way to get this to work in the config file??
2- running from the cmdline works.. but when I do a " ctrlA-d to get
out of the screen session.. I also kill the term!
Is there a way to be able to "launch the screen" but also be able
to kill the screen session, returning to the
shell if the cssh/window...
I could prob run some quick/dirty shell script to fire up the
screen session.. within the window when it gets launched..
but that seems kludgy..
thoughts/comments..
thanks
On Tue, Feb 27, 2018 at 2:44 PM, bruce <badouglas@xxxxxxxxx> wrote:
> Hi.
>
> Testing the cssh process.
>
> I configured the /etc/clusters file to have
> -testcluser foo@1.2.3.4
>
> As user 'foo' I run -- cssh testuser
>
> Process returns:
> Connection to server failed -- (version 11.0)
> No protocol specified
> at /usr/bin/cssh line 2152
>
> As a test, logged in as root ran the same thing.. a term displayed.
>
> So, I've got something misconfigured on the local to run the gui process.
>
> In the /etc/ssh/ssh_config I tested with both
> ForwardX11 yes/no <<<<
>
> with no difference
>
> Looking through the 'net I se a number of possible issues, but as I
> currently work through them, no change.
>
> Thoughts/comments??
>
> Thanks
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
