Package vnc-server is not installed
Connect and share knowledge within a single location that is structured and easy to search. In CentOS 6. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 8 years, 8 months ago. Setting up sudo 1. Setting up openssl 1. Processing triggers for systemd deb10u Processing triggers for man-db 2.
Processing triggers for libc-bin 2. Done E: Unable to locate package libc6:armhf. Done Some packages could not be installed. So, as i have spent much time on raspbian the last 6months i return to ubuntu and upgrade from Skip to content.
Star 2. New issue. Jump to bottom. Labels bug. The vncviewer client will connect to port X where X is an offset of 1,2,3 for Larry, Moe, and Curly respectively, so these ports must be open in the firewall for the IP addresses or subnets of the clients.
The following sections are optional refinements to enhance security and functionality. VNC encrypted through an ssh tunnel You will be connecting through an ssh tunnel.
You will need to be able to ssh to a user on the machine. For this example, the user on the vncserver machine is: larry That account username needs to exist on the target machine, and either password, or keyed ssh access needs to be functional.
The Linux and VNC system usernames and passwords are not required to be identical and are 'not' automatically synchronized. That is, remote users able and baker may each have differing credentials to set up the ssh tunnel to the remote VNC server, but if each uses the larry account, they will use the same VNC password. If not, performance may be very poor! Recovery from a logout Not implemented for CentOS 6 If you logout of your desktop manager, it is gone!
We added a line to xstartup to give us an xterm where we can restart our window manager. For gnome, enter gnome-session. For kde, enter startkde. Remote login with vnc-ltsp-config To allow remote login access via a vnc-client to the Centos system, the RPM packages named vnc-ltsp-config and xinetd can be installed.
When a vnc-client connects to one of the configured ports, the user will be given a login screen. When a user logs out, the session is gone. A major advantage of using the vnc-ltsp-config setup is the reduction of system resource utilization compared to the standard "per-user setup".
No user processes will be started or memory consumed until a user actually logs into the system. Also, no pre-thought for user setup is needed eg skip all of the manual individual user setup for vnc-server. But then, I have not used a GUI for Linux for the past years, only doing a little administration through the shell here and there.
Almost related, but will it be possible to put a vnc tutorial for Mint 17 also? Tigervnc might be working fine on.. We have always configured remote access to VNC through xinetd. Doing so allows for more security controls on who can remotely access the system. So all around it is a better configuration more secure access, Linux login controls and multiple sessions with one config albeit a little more complex to set up.
So that preamble all leads up to a question. Do you know of anyone that has posted the xinetd setup for a CentOS 7 remote vnc desktop? Follow the guide but at the last few steps Starting the vnc service as root I get command not found…. Feb 26 server. Once logged in using VNC client, the session is different from the actual system. Is there a way to get the same session? Dec 09 localhost. All Rights Reserved.