Skip to content
Snippets Groups Projects
Commit 264fb736 authored by Jan Siwiec's avatar Jan Siwiec
Browse files

Update vnc.md

parent 195b487e
No related branches found
No related tags found
4 merge requests!368Update prace.md to document the change from qprace to qprod as the default...,!367Update prace.md to document the change from qprace to qprod as the default...,!366Update prace.md to document the change from qprace to qprod as the default...,!323extended-acls-storage-section
......@@ -12,7 +12,7 @@ The recommended clients are [TightVNC][b] or [TigerVNC][c] (free, open source, a
VNC server password should be set before the first login. Use a strong password.
```console
[username@login2 ~]$ vncpasswd
$ vncpasswd
Password:
Verify:
```
......@@ -28,7 +28,7 @@ Start by **choosing your display number**.
To choose a free one, you should check currently occupied display numbers - list them using the command:
```console
[username@login2 ~]$ ps aux | grep Xvnc | sed -rn 's/(\s) .*Xvnc (\:[0-9]+) .*/\1 \2/p'
$ ps aux | grep Xvnc | sed -rn 's/(\s) .*Xvnc (\:[0-9]+) .*/\1 \2/p'
username :79
username :60
.....
......@@ -45,7 +45,7 @@ Based on this requirement, we have chosen the display number 61, as seen in the
Start your remote VNC server on the chosen display number (61):
```console
[username@login2 ~]$ vncserver :61 -geometry 1600x900 -depth 16
$ vncserver :61 -geometry 1600x900 -depth 16
New 'login2:1 (username)' desktop is login2:1
......@@ -56,7 +56,7 @@ Log file is /home/username/.vnc/login2:1.log
Check whether the VNC server is running on the chosen display number (61):
```console
[username@login2 .vnc]$ vncserver -list
$ vncserver -list
TigerVNC server sessions:
......@@ -67,7 +67,7 @@ X DISPLAY # PROCESS ID
Another way to check it:
```console
[username@login2 .vnc]$ ps aux | grep Xvnc | sed -rn 's/(\s) .*Xvnc (\:[0-9]+) .*/\1 \2/p'
$ ps aux | grep Xvnc | sed -rn 's/(\s) .*Xvnc (\:[0-9]+) .*/\1 \2/p'
username :61
username :102
......@@ -130,7 +130,7 @@ Start the VNC server using the `vncserver` command described above.
Search for the localhost and port number (in this case 127.0.0.1:5961):
```console
[username@login2 .vnc]$ netstat -tanp | grep Xvnc
$ netstat -tanp | grep Xvnc
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:5961 0.0.0.0:* LISTEN 24031/Xvnc
......@@ -191,7 +191,7 @@ Uncheck both options below the slider:
If the screen gets locked, you have to kill the screensaver. Do not forget to disable the screensaver then.
```console
[username@login2 .vnc]$ ps aux | grep screen
$ ps aux | grep screen
username 1503 0.0 0.0 103244 892 pts/4 S+ 14:37 0:00 grep screen
username 24316 0.0 0.0 270564 3528 ? Ss 14:12 0:00 gnome-screensaver
......@@ -203,7 +203,7 @@ username 24316 0.0 0.0 270564 3528 ? Ss 14:12 0:00 gnome-screensa
You should kill your VNC server using the command:
```console
[username@login2 .vnc]$ vncserver -kill :61
$ vncserver -kill :61
Killing Xvnc process ID 7074
Xvnc process ID 7074 already killed
```
......@@ -211,7 +211,7 @@ Xvnc process ID 7074 already killed
or:
```console
[username@login2 .vnc]$ pkill vnc
$ pkill vnc
```
!!! note
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment