Skip to main content

Configuring The TigerVNC Server In Fedora 21/RHEL7/CentOS7

Introduction: 
TigerVNC (Tiger Virtual Network Computing) is a system for graphical desktop sharing which allows you to remotely control other computers. TigerVNC works on the client-server network. A server shares its output (vncserver) and a client (vncviewer) connects to the server. 



1. Installing VNC Server

~]# yum install tigervnc-server

Now we need to copy the configure the configuration file as following:

~]# cp /lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@.service

Now need to edit the file, and here we can mention the name of the user which we want to allow for desktop sharing:

~]# vim /etc/systemd/system/vncserver@.service

replace USER with the actual user name. Leave the remaining lines of the file unmodified.

Following is the actual line in the file:
ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024"
PIDFile=/home/USER/.vnc/%H%i.pid

Here we need to write Username instead of USER, EX: if my username is vchauhan then line would we like that:
ExecStart=/sbin/runuser -l vchauhan -c "/usr/bin/vncserver %i -geometry 1280x1024"

3. save the changes and exit from file.

4. To make the changes take effect immediately, issue the following command:

~]# systemctl daemon-reload


5. Set the password for the user or users defined in the configuration file. Note that you need to switch from root to USER first.

~]# su – vchauhan
~]$ vncpasswd
Password:
Verify:



Configuring VNC Server for Two Users

1. First of all need to set the password for the users which we are going to add into vnc

~]$ su - suresh
~]$ vncpasswd
Password:
Verify:

~]$ su - sonu
~]$ vncpasswd
Password:
Verify:

2. Now need to start the VNC server daemon again:

~]# systemctl start vncserver@:1.service

Note: Here “1” is the display number, we can type any number, after daemon reload a port number will be start from the server, in my example, port number would be: 5901.
we can verify it:

~]# netstat -tupnl | grep 5901

Now we can access the server by using this port using any given user name:

~]# vncviewer localhost:5901


Configuring VNC Server for two users and two different displays

Now if we want to specify the different port number for each user, so every user can have it's own desktop at the same time, we need to specify the port number for them according to following. 

Those commands will start a VNC server for suresh user to start on display 3, and a VNC server for sonu user to start on display 4:


~]# systemctl start vncserver-suresh@:3.service
~]# systemctl start vncserver-sonu@:4.service

Terminating a VNC session

We can disable the service for particular display or user:

~]# systemctl disable vncserver@:display_number.service


For the run time only we can disable the service also:


~]# systemctl stop vncserver@:display_number.service



Done........

Comment it !! Share it !!


Comments

Post a Comment

Popular posts from this blog

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image downloaded we can start a contai
Post a Comment
Read more

Remote Systems Management With Cockpit

The cockpit is a Red Hat Enterprise Linux web-based interface designed for managing and monitoring your local system, as well as Linux servers located in your network environment. In RHEL 8 Cockpit is the default installation candidate we can just start the service and then can start the management of machines. For RHEL7 or Fedora based machines we can follow steps to install and configure the cockpit.  Following are the few features of cockpit.  Managing services Managing user accounts Managing and monitoring system services Configuring network interfaces and firewall Reviewing system logs Managing virtual machines Creating diagnostic reports Setting kernel dump configuration Configuring SELinux Updating software Managing system subscriptions Installation of cockpit package.  [root@rhel8 ~] #  dnf   install cockpit cockpit-dashboard  -y  We need to enable the socket.  [root@rhel8 ~] #  systemctl enable --now cockpit.socket If firewall is runnin
Post a Comment
Read more

Containers Without Docker on RHEL/Fedora

Docker is perfectly doing well with the containerization. Since docker uses the Server/Client architecture to run the containers. So, even if I am a client or developer who just wants to create a docker image from Dockerfile I need to start the docker daemon which of course generates some extra overhead on the machine.  Also, a daemon that needs to run on your system, and it needs to run with root privileges which might have certain security implications. Here now the solution is available where we do not need to start the daemon to create the containers. We can create the images and push them any of the repositories and images are fully compatible to run on any of the environment.  Podman is an open-source Linux tool for working with containers. That includes containers in registries such as docker.io and quay.io. let's start with the podman to manage the containers.  Install the package  [root@rhel8 ~] # dnf install podman -y  OR [root@rhel8 ~] # yum
1 comment
Read more