<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Super. That all went great. Thanks. <div><br></div><div>Chris </div><div><br><div><div>On Feb 23, 2014, at 12:32 PM, Ken Causey <<a href="mailto:ken@kencausey.com">ken@kencausey.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On 02/23/2014 11:28 AM, Ken Causey wrote:<br><blockquote type="cite">On 02/23/2014 10:12 AM, Chris Cunnington wrote:<br><blockquote type="cite">I could not figure how Chris Muller was constantly logged in all the<br>time. Every time I logged in I typed who to see if anybody's around.<br>The :1 told me that VNC was likely involved, but I didn't realized it<br>was its own process. I was talking to Ken about using Ian's RFB.<br>I recall a conversation about six-eight months about where Levente<br>recommended TightVNC (IIRC). I figure I'll switch to that and we can<br>make it the<br>standard for box4. I assume that this single process can have another<br>port such as 5902/:2 added to it?<br><br>Chris<br><br></blockquote><br>Yes, with external VNC there is an external process that acts as an X<br>client that interfaces to the VNC protocol.<br><br>Chris is logged in because, well it is in some sense a full X desktop so<br>you can have multiple programs running, and he has a terminal open on<br>the VNC he started for his <a href="http://source.squeak.org">source.squeak.org</a> mirror and he is logged in<br>in it.<br><br>Using external VNC is only slightly more complicated that RFB.<br></blockquote><br>s/that/than/<br><br><blockquote type="cite"><br>1. Login and stay in your home directory then<br><br>mkdir .vnc<br><br>2. Using your favorite text editor add a xstartup file to that<br>directory, this is a script that is started after the X client is open<br>to start X server programs. Feel free to copy mine at<br><br>/home/ken/.vnc/xstartup<br></blockquote><br>This should of course be<br><br>/home/kencausey/.vnc/xstartup<br><br><blockquote type="cite"><br>as a starting point.<br><br>3. Run<br><br>vncpasswd<br><br>to set your password<br><br>4. Run<br><br>vncserver<br><br>This will report back to you your port number which you would then<br>specify on your local VNC client. If :1 is in use but not :2 then you<br>will get :2, and so on.<br><br>Not that in ~/.vnc there are a couple of files created that can be of<br>some value. There is a .pid file that stores the process ID of the<br>xtightvncserver process. More usefully there is a .log file that logs<br>any stdout/stderr from the processes. For example if squeak fails to<br>start or crashes you can find useful info there.<br><br>Finally, when you are done, run<br><br>vncserver -kill :<port number><br><br>To stop the VNC server and all the programs that were started under it.<br> <port number> is of course the number reported when you ran vncserver<br>before and what you used to connect beyond of course the hostname.<br><br>Hopefully this makes it reasonably clear.<br><br>Ken<br><br></blockquote><br>P.S. And just to be sure your realize it, once you have done this once, unless of course you want to modify your xstartup or set a new password, you can just start at step 4 in the future.</div></blockquote></div><br></div></body></html>