Hi!
> Not that this is sure to solve your problem, but it's a possibility:
> ssh daemons can be configured to prohibit X forwarding. Try
>
> ssh -v -l <user> <system> <x app>
Use the above if your sure you enabled x-forwarding in your ~/.ssh/config
or in /etc/ssh/ssh_config. If not, a better idea would be to use
ssh -v -X -l <user> <system> <x app>
instead. And an other one: some x-apps behave curious if started this way.
They depend on being started in an interactive shell. In such case you
might even be better of using:
ssh -v -X -l <user> <system> /bin/bash -l -i -c "<x app> &"
to make sure your x-app is seeing an interactive shell environment!
BTW: did you set "export DISPLAY=:0.0" ("setenv DISPLAY :0.0" for csh)
before calling ssh? SSH wont forward X if no display variable was set
before. It's regardless of an X-server beeing started. Just make shure
"DISPLAY" exists and is exported.
> to see what ssh reports regarding whether X forwarding was actually
> established, and/or check the sshd_config file on the remote machine
> (if you have permission; otherwise, ask the admin.)
--
Thomas
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
