Re: Accessing RedHat Linux 8 system
Re: Accessing RedHat Linux 8 system
- Subject: Re: Accessing RedHat Linux 8 system
- From: zol <email@hidden>
- Date: Wed, 26 Feb 2003 04:00:43 -0800
Yep just try to do
#ssh login@box -X
from an xterm on your mac.
Then
#echo DISPLAY
on the RH box to see if it is set correctly.
( should be localhost:10.0 )
if not set it with
export DISPLAY=localhost:10.0 ( or setenv if you use tcsh )
and launch an xterm to see if it's ok.
-z
> From: Jonas Maebe <email@hidden>
> Date: Wed, 26 Feb 2003 10:02:37 +0100
> To: email@hidden
> Subject: Re: Accessing RedHat Linux 8 system
>
> On woensdag, feb 26, 2003, at 06:05 Europe/Brussels, bryan wrote:
>
>> Same sort of problem here (I think) on LinuxPPC. Beige G3 266:
>>
>> habanero =Mac OS X 10.2.4 w/ X11 (second beta)
>> ecstasy =LinuxPPC 2000 Q4
>>
>> [habanero:~] bryan% ssh -X ecstasy uname -a
>
> Are you doing this from inside an XTerm or from within Terminal? In the
> latter case, you first have to do a
>
> setenv DISPLAY :0
>
> (if you're using the default tcsh, for bash it's "export DISPLAY=:0").
>
>> Linux ecstasy 2.2.18-4hpmac #1 Thu Dec 21 15:16:15 MST 2000 ppc unknown
>>
>> [habanero:~] bryan% ssh -X ecstasy /usr/bin/same-gnome
>> connect habanero port 6000: Connection refused
>
> I think this shows that "same-gnome" is not using the ssh tunnel, since
> it would not try to connect to port 6000 of habanero in that case.
>
>> Gdk-ERROR **: X connection to ecstasy:10.0 broken (explicit kill or
>> server shutdown).
>>
>> I asked a while ago but got no replies as X11 the second beta had just
>> been released.
>>
>> My best guess is that everyone thought that maybe the problem was
>> fixed in this new version....
>
> Nothing was broken in the first release regarding ssh forwarding and
> it's still not broken in the second release. This kind of problems is
> almost always due to configuration issues. The most likely causes are
>
> a) "X11Forwarding yes" is not set in the /etc/sshd_config file of the
> machine you are ssh'ing to
> b) you have *not* set the DISPLAY environment variable to :0 or didn't
> start X11.app on the local machine before you ssh'd to the remote host
> (the fact that X11.app must already be started is strange, because I
> seem to remember that this was not necessary for XDarwin)
> c) you *do* set the DISPLAY environment variable in a login script on
> the remote server, so it overrides the one ssh has set
> d) (very unlikely in this case) you are trying to run a very old X
> program and are using sshd 3.1 (or maybe even 3.0, I don't remember) or
> higher on the remote server. In that case, you have to add
> "X11UseLocalhost no" to the sshd_config on the remote machine. Note
> that adding this option is potentially more insecure (though there are
> no known exploits afaik) that the default setting of "yes".
>
>
> Jonas
> _______________________________________________
> x11-users mailing list | email@hidden
> Help/Unsubscribe/Archives:
> http://www.lists.apple.com/mailman/listinfo/x11-users
> X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
> Report issues, request features, feedback:
> http://developer.apple.com/bugreporter
> Do not post admin requests to the list. They will be ignored.
_______________________________________________
x11-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/x11-users
X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
Report issues, request features, feedback: http://developer.apple.com/bugreporter
Do not post admin requests to the list. They will be ignored.