yum update server + Network question.

[Rick Stevens]

Graeme Nichols wrote:
> On Sat, 2004-06-19 at 02:22, Rick Stevens wrote:
> 
>>Graeme Nichols wrote:
>>
>>>On Thu, 2004-06-17 at 02:02, Rick Stevens wrote:
>>>
>>>
>>>
>>>>Ah.  I usually refer to that as "cockpit error" or "a short between
>>>>the keyboard and ground".  I believe the scientific term is "Huh?" ;-)
>>>>
>>>>
>>>>
>>>>>Anyway, things are
>>>>>lookin' good now!
>>>>
>>>>Glad to hear it.
>>>
>>>
>>>Hi Rick, just further on the internet access for my laptop, I suppose I
>>>could have stuck with ssh and logged into my desktop machine and run Moz
>>>or Evo from the desktop machine as that works nicely and it has the
>>>benefit of keeping all my emails in the one place on the one machine.
>>>Ahhhh, options... options.... ain't Linux luvly.
>>
>>Take a look at running a VNC server on your desktop and a VNC client on
>>your laptop.  Your laptop then gives you full GUI access to your
>>desktop.  This can be tunneled via SSH as well for security.  Very cool.
> 
> 
> Hello Rick, a question on vnc, I had vnc already installed on my desktop
> machine (I did a 'complete' install when I installed RH8) and started
> the vnc server on my desktop so:
> 
> [graeme at barney graeme]$ vncserver
> 
> New 'X' desktop is barney.localdomain:1
> 
> Starting applications specified in /home/graeme/.vnc/xstartup
> Log file is /home/graeme/.vnc/barney.localdomain:1.log
> 
> 
> 
> It comes up as above. If I then start vncviewer I am asked for my
> password etc and get the Xwindow (fullscreen) with the big X mouse
> pointer but no window manager. xstartup contains the following:
> 
> [graeme at barney graeme]$ cat .vnc/xstartup
> #!/bin/sh
> 
> # Red Hat Linux VNC session startup script
> exec /etc/X11/xinit/xinitrc
> 
> It doesn't matter if I comment out the exec line above the window I get
> is always the same (I think it is twm but I'm not sure). If I put a
> command in xstartup, eg evolution, it doesn't start, just get the
> Xwindow with the big X mouse pointer. F8 to get the popup works OK in
> the window but nothing else.

You need to edit your "~/.vnc/xstartup" file ("~" means your home
directory) and uncomment the two lines:

	unset SESSION_MANAGER
	exec /etc/X11/xinit/xinitrc

to get the window manager you expect.  If you edit that file, you must
kill and restart the VNC server:

	vncserver -kill :1
	vncserver

as ~/.vnc/xstartup is only read when the VNC server starts.

> 
> If I try from my laptop using the command 'vncviewer -via 192.168.1.2
> barney:1' it doesn't work. 192.168.1.2 is the IP address of the laptop.
> If I try 'vncviewer -via 192.168.1.1 barney:1 it works to the point
> where it simply stops after entering the password. Hitting 'enter'
> brings up the message 'couldn't read password' or similar and the
> terminal prompt re-appears. 192.168.1.1 is the IP address of the
> desktop. The vnc log file follows:
> 
> [graeme at barney graeme]$ cat .vnc/barney.localdomain:1.log
> 30/06/04 14:48:52 Xvnc version 3.3.3r2+tight1.2.2
> 30/06/04 14:48:52 Copyright (C) AT&T Laboratories Cambridge.
> 30/06/04 14:48:52 All Rights Reserved.
> 30/06/04 14:48:52 See http://www.uk.research.att.com/vnc for information
> on VNC
> 30/06/04 14:48:52 Desktop name 'X' (barney.localdomain:1)
> 30/06/04 14:48:52 Protocol version supported 3.3
> 30/06/04 14:48:52 Listening for VNC connections on TCP port 5901
> 30/06/04 14:48:52 Listening for HTTP connections on TCP port 5801
> 30/06/04 14:48:52   URL http://barney.localdomain:5801
> gnome-session: you're already running a session manager
> 
> 30/06/04 14:50:28 Got connection from client 192.168.1.1
> 30/06/04 14:50:28 Protocol version 3.3
> 30/06/04 14:50:31 Client 192.168.1.1 gone
> 30/06/04 14:50:31 Statistics:
> 30/06/04 14:50:31   framebuffer updates 0, rectangles 0, bytes 0

The command to use is

     vncviewer -via ipaddress-of-remote ipaddress-of-remote:1

In your case:

	vncviewer -via barney barney:1

(assuming 192.168.1.1 is barney).  Remember that you're tunneling via
the REMOTE machine's SSH, not the local one.  As to the password issue,
try stopping the VNC server on barney:

	vncserver -kill :1

then going into your ~/.vnc directory and deleting the "passwd" file
there.  Then restart the VNC server and it'll ask you for a new
password.  Remember that when the VNC _client_ asks you for a password,
it's THIS password (the one you gave to the VNC server) that it wants.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-     If you can't beat your computer at chess...try kickboxing!     -
----------------------------------------------------------------------