HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Problem running remote X applications on a Mac OS ...
Operating System - Linux
1832890
Members
2036
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2008 11:07 AM
10-06-2008 11:07 AM
Problem running remote X applications on a Mac OS X 10.5.5 Intel system
Hi there --
One of our users is trying to connect to a remote Linux system from his Mac, and then run several X applications on that system. He opens up an X terminal, and first types in the following command:
xhost +
He then connects via ssh to the remote system using the following command syntax:
ssh -X -l
Once he is on the remote system, his command shell is tcsh, and the following command is entered:
setenv DISPLAY:0.0
When he tries to start xemacs, or any X application for that matter, he gets the following error message:
X server not responding
Several other users have used the above procedure, and have been able to start the remote X applications without a problem.
Has anyone seen this, and know what the fix is to this problem? Thanks.
One of our users is trying to connect to a remote Linux system from his Mac, and then run several X applications on that system. He opens up an X terminal, and first types in the following command:
xhost +
He then connects via ssh to the remote system using the following command syntax:
ssh -X -l
Once he is on the remote system, his command shell is tcsh, and the following command is entered:
setenv DISPLAY
When he tries to start xemacs, or any X application for that matter, he gets the following error message:
X server not responding
Several other users have used the above procedure, and have been able to start the remote X applications without a problem.
Has anyone seen this, and know what the fix is to this problem? Thanks.
A Journey In The Quest Of Knowledge
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2008 12:41 PM
10-06-2008 12:41 PM
Re: Problem running remote X applications on a Mac OS X 10.5.5 Intel system
I don't normally deal with it, but ...
> [...] a remote Linux system [...]
How "remote"? (How many X-blocking firewalls
in between?)
I thought that "ssh -X" was supposed to deal
with all the DISPLAY stuff by itself. What
happens if you leave out this step?:
setenv DISPLAY:0.0
Around here (Mac OS 10.4.11), "man ssh" says:
[...]
X11 FORWARDING
[...]
The user should not manually set DISPLAY.
Forwarding of X11 connections can be
configured on the command line or in
configuration files.
[...]
Doing it yourself bypasses the X forwarding
stuff in SSH. You can do that, but it does
make the "-X" rather pointless, and it also
means that you need to get at port 6000 on
the Mac instead of just the SSH stuff.
There's also sshd configuration on the server
side to worry about (about which I also know
little).
> [...] a remote Linux system [...]
How "remote"? (How many X-blocking firewalls
in between?)
I thought that "ssh -X" was supposed to deal
with all the DISPLAY stuff by itself. What
happens if you leave out this step?:
setenv DISPLAY
Around here (Mac OS 10.4.11), "man ssh" says:
[...]
X11 FORWARDING
[...]
The user should not manually set DISPLAY.
Forwarding of X11 connections can be
configured on the command line or in
configuration files.
[...]
Doing it yourself bypasses the X forwarding
stuff in SSH. You can do that, but it does
make the "-X" rather pointless, and it also
means that you need to get at port 6000 on
the Mac instead of just the SSH stuff.
There's also sshd configuration on the server
side to worry about (about which I also know
little).
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP