Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm trying to start a GUI application on remote server. My goal is to be able to open SSH client, run the startup script, like so
and have it started and open its window on the screen of the remote machine.
I would really like not to use VNC or transfer X session to my local machine. I don't need to see the window on my local machine - just need to start the app. I do, however, want the application window to be visible on the screen of the remote machine.
Is the any way to do what I'm trying to achieve? I'm running SLES 9 on the remote server with XDM and FVWM.
Sorry, if this question has been answered before. I've been looking for info on this for some time with no success.
make sure you have acces to the remote display. Make sure that ssh is not doing X-forwarding (read manpage) and set your display manually to :0. that should put the app on the first display on the remote host.
Now I know why I was having trouble getting results before. This works only if I have already logged in through X. So if I have an X session open on the remote computer, i.e. I have manually logged in using graphical interface. If I restart remote server and don't login using graphical prompt, I cannot start the application remotely, get the following error:
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 220.127.116.11, KDE 3.5.8 and KDE 4.0 beta, Plu
Yes using the ssh -Y is great but I think he need to start a gui type app on the remote machine and it needs to remain on the remote machine. It is confusing not knowing exactly what ./runapp.sh is doing. The more I think about it unless the gui is running then the app will never start. Even if a vncserver on display 2 is created then the app starts on display 2. It can be sent to display 0 but once again the gui on display 0 needs to be running. Only way out I see is to setup the login manager to autologin with a default user account. Then if rstarted it will auto login and start the gui session. My thoughts are related to KDE and Gnome. More simplier guis like icevm or twm might be able be started but again that will be on display 0 and if you really what KDE or Gnome it will need to be started to display1 and so on.
Better stop there I keep running into a block wall.
true he wanted to program to show up on the remote host, so DISPLAY and xhost is appropriate if he is not the user running the desktop.
But even when [xkg]dm is waiting for a login, the X-server is already running. I suppose with the right xhost stuff, you could make it display a program other than xdm.
To me it seems you need to run vncserver and set it to display 1 or 2. That way that gui as that user is already up. Then do the same as above except point to display 2
This might be an option. Not a prefered one, but if nothing else works, I guess I will have to try doing that.
You shouldn't do any DISPLAY or xhost stuff or anything, just do "ssh -Y ..." when you connect using ssh and it will forward X for you.
Please read from the beginning of the post carefuly before replying.
It is confusing not knowing exactly what ./runapp.sh is doing.
Just a script that starts a server Java app. Application uses GUI so, unfortunately, I'm forced to run X or have to rewrite the app.
Only way out I see is to setup the login manager to autologin with a default user account. Then if rstarted it will auto login and start the gui session.
That what I'm thinking too. Unfortunately my knowledge of X is close to 0. The Linux server doesn't run KDE or Gnome, we're trying to keep it as light as possible. I was already forced to install X just for this app. What we're running right now is XDM and FVWM. Can anyone help me configure this machine so it can autologin with some user account at boot, have the GUI running and then autostart the app.
Man, what an cumbersome way of doing things... but what else am I going to do?