They need to know your VNC password (and you have picked a strong enough passphrase that can't be guessed, right?)Īll in all, the risks should be minimal.For being able to log into Snellius they need to have their IP address whitelisted and have valid login credentials.Data sent between the remote VNC desktop on Snellius and the client running locally is encrypted using an SSH tunnel.In theory, somebody also logged into Snellius could try to connect to the VNC server you started on a render node. Isn't it possible that somebody other than me snoops on my VNC session? When you find that the Alt-key seems to be "stuck" in your VNC viewer simply press and release Alt. This is probably because the Alt keypress event is captured by the VNC viewer, but the subsequent TAB keypress will take away keyboard focus and so the viewer application never receives a release event for the Alt key, thinking it is still pressed when you switch back to it. Some VNC viewers (and versions) have problems when you're using Alt-TAB to switch to and from the viewer application.
After switching between my VNC viewer and some other application on my local machine the VNC viewer seems to get confused about the keys I press E.g., for a VNC server running on gcn10:1 check gcn10.1.log. $ vnc_desktop -reservation= Something strange is going on with my VNC session, is there a VNC server log file I can check? How do I run the VNC job within a SLURM reservation? Yes, use the -r x option with vnc_desktop.Another option is to set the environment variable VNC_DESKTOP_RESOLUTION in your shell's startup script, again to x, so you don't have to use -r each time. The desktop resolution is quite low in the VNC session, can I change it? The VNC server used on Snellius and Lisa is actually TurboVNC. Note that "Screen Sharing" on MacOS is not usable as a VNC viewer, at least, not in our tests.
Plus, we have seen issues with the TightVNC client not supporting the required authentication methods we use on the server side. TightVNC and RealVNC might also work, but sometimes seems to have noticeable lower performance (especially on Windows). In principal any viewer supporting the VNC protocol can be used, but the two mentioned are well maintained and provide good performance. Of these two, TigerVNC has a nicer GUI and appears to have slightly better performance. TurboVNC and TigerVNC are good choices and the ones we recommend. That xrandr setting isn't persistent, so needs to be re-entered after each reboot, creating a script in ~/Startup is one way to achieve that.VNC There seem to be a lot of VNC viewers out there, which ones do you recommend? With the server ethernet connected to the net downloads to that are also much quicker. I prefer to use x0vncserver as my vnc server choice (rather than directly invoking x11vnc) and over a local wifi LAN that runs really well, displaying youtube videos near as good as if you were viewing the video using the laptop.
Tigervnc resolution full#
values that enlarged (scaled) laptop screen size can be made to look OK, and if in tigervnc you turn off the Screen tab options for resizing, tick the full screen option, then once vnc connected it also looks good, full screen with the full screen fitting the laptop full screen and no actual panning. With some tweaking of default font sizes, Xft.dpi. scale values are 1440/1366 width scale and 900/768 height scale. On the laptop adjusts its visual area to match that of the vnc servers i.e. Running xrandr indicates that laptop screen device name to be eDP, yours might be VGA-0 or suchlike - in which case modify the eDP parameter accordingly. My laptop from where I vnc into that server has a 1366x768 resolution. My vnc server, a old acer desktop PC, runs at 1440x900 resolution. If you run a vnc server on one box/device that has a different screen resolution to the vnc client box/device then one way to resolve that difference is to use xrandr scaling.
0 kommentar(er)
