Moving Exceed xterm windows (read as: removing exceed xterm windows...)

Corné Beerse cbeerse "at"
Wed Jan 28 10:29:01 2004

Anant Rao wrote:

> Hello,
> I'm using VNC client on windows 2k box and vnc server on another win2k box.
>>From the box running vnc server, I run xterm client (Exceed). If I move any
> of those xterm windows from vnc client on the windows, the Exceed freezes. I
> have to kill the xterm client window on  the vnc server windows box  as a
> way out.
> Only Exceed xterm client windows freeze. The other apps on the box are ok.
> Is this observed before? If so, any help much appreciated.

I donnot know the problem. I do know Exceed, it is an X11 server that runs on a 
PC to view remote Xapplications. Hence I see you have a desktop, viewing an 
intermediate system that shows a remote display.

Best way is to remove the intermediate system. You can install exceed on your 
local system but you ask the vnc area for a solution. Hence, install vnc on the 
remote unix system, there is a vnc for roughly every unix flavour around. Then 
you can use vnc from your desktop and gain direct access to the Xsession with 
the xterm, avoiding all overhead from exceed and such.

THe basic vnc setup let you, the user, start and stop the session and can be 
installed and used in userspace, without any need for root-access or such.

Better to let the sysadmin configure vnc in the unix system. He can do it 
following (this is my 
favorite for normal usage)

And I recently posted an other setup to this list, find it attached once more.

Both setups are based on LinuxRedhat but they can be used as a guideline on 
other systems.

> Thanks,
> _______________________________________________
> VNC-List mailing list
> VNC-List "at"
> To remove yourself from the list visit:
Return-Path: <vnc-tight-list-admin "at">
Received: from (
  []) by (Postfix) with ESMTP id
  1345B6E3C8 for <cbeerse "at">; Fri, 23 Jan 2004 11:07:06 +0100
Received: from localhost ([] by with esmtp (Exim 4.30) id
  1Ajy0n-0003j8-Sd; Fri, 23 Jan 2004 01:54:01 -0800
Received: from ([] by with
  esmtp (Exim 4.30) id 1Ajy02-0003dN-ON for
  vnc-tight-list "at"; Fri, 23 Jan 2004 01:53:14 -0800
Received: from ([] by with esmtp (Exim 4.30) id 1Ajy02-0005Kd-18
  for vnc-tight-list "at"; Fri, 23 Jan 2004 01:53:14
Received: by id <119081>; Fri, 23 Jan 2004 11:19:46 +0100
Message-Id: <04Jan23.111946cet.119081 "at">
From: =?ISO-8859-1?Q?Corn=E9_Beerse?= <cbeerse "at">
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4)
  Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: vnc-list "at", vnc-tight-list "at"
Subject: Xvnc as a X-server (optionally replacing the console Xserver)
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by See for more details. Report problems to
Sender: vnc-tight-list-admin "at"
Errors-To: vnc-tight-list-admin "at"
X-BeenThere: vnc-tight-list "at"
Precedence: bulk
List-Unsubscribe: <>,
  <mailto:vnc-tight-list-request "at">
List-Id: TightVNC list <>
List-Post: <mailto:vnc-tight-list "at">
List-Help: <mailto:vnc-tight-list-request "at">
List-Subscribe: <>,
  <mailto:vnc-tight-list-request "at">
List-Archive: <>
X-Original-Date: Fri, 23 Jan 2004 10:52:57 +0100
Date: Fri, 23 Jan 2004 10:52:57 +0100

This is a description on how to use Xvnc as the Xserver. It is jet an other way 
to create an always running vnc session on unix/linux. It is based on RedHat 9 
but I think it can easy be moved to every unix that has a Xvnc binary.

My goal was to create a linux server that has a text console (for RedHat: as if 
running in runlevel 3) but still has gdm available (actually running runlevel 
5). Roughly, I just replaced the Xserver (XFree86 on linux) with Xvnc.

I first installed the vncserver packages from the distribution and start 
`vncserver` at least once to have a vnc password file.

Then (sidestep) I installed I don't expect it is 
needed but for me it is the reason to run in runlevel 5 and not in runlevel 3.

The real work is in getting Xvnc used as an Xterminal that runs on the same 
host. For GNOME (gdm) users: edit '/etc/X11/gdm/gdm.conf':
- disable VTAllocation (about line 104)
- add server definitions (at the end, the double inserted lines are continuation 
of the previous line, combine them.)
	# vncsession, using vncpassword from root
	name=ROOTVNC server
	command=/usr/bin/Xvnc -geometry 800x600 -depth 8 -rfbwait 120000
		-rfbauth /root/.vnc/passwd
	# vncsession, using no vncpassword
	name=FREEVNC server
	command=/usr/bin/Xvnc -geometry 800x600 -depth 8 -rfbwait 120000
		-alwaysshared -dontdisconnect
- in the [servers] section, add and/or replace lines that indicate an Xserver:
	# disable the X session on the console
	# use roots vncsession on :0
	# use the free-access vncsession on :4
Now restart gnome (or the entire machine) and see the console stays in its text 
mode and there are 2 vnc sessions running: ONe at `vncviewer machine:0` that 
uses the vncpassword of root and an other one at `vncviewer machine:4` that has 
no vncpassword. All provide a login session.

To get the same setup with a KDE or XDM session, it is even simpler. Edit 
'/etc/X11/xdm/Xservers': add the next lines (and comment out all others). 
WRAPWARNING: each line is either comment or it starts with the same word as it 
ends (:0 to :0 and :4 to :4).
	# disable the X session on the console
	#:0 local /usr/X11R6/bin/X
	# vncsession :0, using vncpassword from root.
	:0 ROOTVNC local /usr/bin/Xvnc -geometry 800x600 -depth 8 -rfbwait
		120000 -rfbauth /root/.vnc/passwd :0
	# vncsession :4, no vncpassword.
	:4 FREEVNC local /usr/bin/Xvnc -geometry 800x600 -depth 8 -rfbwait
		120000 -alwaysshared -dontdisconnect :4

Now restart the display manager (or the machine) and...

Detail, if you want to keep the X11 server on the console (not have the :0 vnc 
session): you might need to add '-vt7' to the 'command=/usr/X11R6/bin/X -vt7' line.

If I can find some time, I might put this description on a website some time. If 
others want to do so, please do. If I come acros any other system (HP-UX might 
be the first) I might mail an update. Be free to test it on any other system. 
Most likely you only need to update the Xservers file according the above 
/etc/X11/xdm/Xservers description.


The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
TightVNC mailing list, VNC-Tight-list "at"