The opportunities of this method are endless. Some systems are customized heavily, it depends on the global ssh client and server configurations but if you didn’t manage to get the GUI clock on your desktop try this: If you want to get the prompt back and start the GUI as well put & at the end of the command like: The result of this should be an appearing GUI clock on your Linux desktop. That’s all we need! Now open up a terminal on your Linux GUI desktop, log into your remote server with an indication of using X11 forwarding: It’s the easiest and the most secure, many distributions are set to enable this so let’s check it out:ĭesktop:~ # grep X11Forwarding /etc/ssh/sshd_config No GUI desktop or X server should be running anymore. Getting the remote server readyĬreate an ssh session then switch the remote server back to runlevel 3 if it’s not already: Do not forget to turn off AppArmor and SuSEFirewall services neither. You should try these in your test environment unless you are sure that you would have no issues on your production systems! These could cause major security threats, only enable these on trusted, firewall protected private networks. It’s no issue on Linux, they all come with it unless you unselected it during installation. We can run all installed GUI application and display them anywhere in our network on any desktop, server where an appropriately configured X server is available. Hence I usually configure my servers to start up in runlevel 3 which is the multi user environment without GUI, it’s like turning GUI off but have everything else. It’s actually pretty unnecessary for most servers to run GUI desktop, it’s just a wasting your resources, opening unnecessary ports, weakening security, risking system stability due to running something you don’t actually need. Using these in a Linux environment is the focus of this guide. Nowadays we rarely sit in front of the server or desktop we are about to manage, we do these remotely, remote control utilities have come a long way. It’s very important especially in a server environment. When you run a GUI application you actually display that through your local X server, that’s the default behavior unless you tell your system where you want to display your GUI application. Your system starts an X server in the background at the boot process when you reach runlevel 5, it is supposed to be the default on most distributions. On UNIX the graphical display is managed in the same fashion as many other common services with client-server components. This guide is based on SUSE Linux Enterprise Desktop 10 (SLED) and the default display manager Gnome but should be very similar to OpenSUSE or other releases. I’m still a CLI guy, barely use the GUI but nowadays more and more GUI tools added to many Linux flavors so it’s unavoidable to use them every now and then. In this guide I’ll explain how to manage X displays (GUI) on Linux servers, desktops in best possible way and remotely.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |