FilesSubmittedBranchesLabelsClientsUsersJobsHelp
Tree viewShow file textShow revision historyShow/hide recent activityInformation
Recent activity in //depot/ttul/www/vnc.html/...
342003/07/04zz9vnc.html: typos. 'completly'. honestly.
162001/02/10mtxVNC over the ssh tunnel. it's slow, but it's X, from a library. in 2001.
//depot/ttul/www/vnc.html#1

//depot/ttul/www/vnc.html#1 – add change 16 (text) ·revision history

1<html>
2<head>
3<title>VNC Instructions</title>
4</head>
5<body bgcolor="#ffffff" text="#000000" link="#003366" vlink="#336699" alink="#6699cc">
6<font color="#ff0000" size=+5 bold=true>VNC Instructions</font>
7<br><br>
8
9<p>NOTE: You must start a VNC server running before you can connect to it.</p>
10<ul>
11<li>Log into ttul using the regular <a href="ssh/float.html">ssh applet</a>, above.
12<li>At the prompt, type '<code>vncserver</code>' and remember what display it returns.
13If you have never started vncserver before, it will prompt you for a password. You
14can enter either the same password as usual or not -- the VNC password is completly
15independent of the system password.
16<li>Log out
17<li>Start the <a href="ssh/vncfloat.html">VNC viewer</a>: enter your username and
18password, then the display, then your VNC password.
19<li>Hit the 'Connect' button to begin your session.
20</ul>
21
22<p>Note also that VNC is a stateless protocol. When you exit the VNC client, you
23don't kill the VNC server. You can connect again later. However, this means that
24you will have to manually kill your VNC when you are finished with it.</p>
25<ul>
26<li>Log into ttul using the regular <a href="ssh/float.html">ssh applet</a>, above.
27<li>At the prompt, type '<code>killall Xvnc</code>'. This will kill any VNC servers
28you have running, but will not affect other users servers.
29<li>Log out
30</ul>
31
32</body>
33</html>

P4Web/LINUX26X86/2005.1/82295 · Copyright © 1995-2005 Perforce Software · ttul.org