-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On February 20, 2003 01:25 pm, Lucio Chiappetti wrote:
> On Thu, 20 Feb 2003, Grant McDorman wrote:
> > I am sure that removing the xmodmap will fix the problem.
>
> Indeed now it's all OK.

Good.

> Also in any case should it not be sufficient to run xmodmap on the machine
> with the physical console and keyboard attached ? i.e. the one running the
> VNC viewer.  I just tried to call up a dxnotepad session on the other
> machine (the VNC server) in the VNC display and all went OK !

Yes, absolutely.

> > What version of VNC are you running again?
>
> the viewer is 3.3.2 VNC binary distribution from the original ORL site
>
> the server is 3.3.3r1 VNC binary distribution just installed from
> ftp://public.arl.arizona.edu/pub/sware/vnc-current_osf.tgz

I think that is old enough that it may have the problem with >2 keysyms per 
key. A new version won't have that problem; however since it's working for 
you now you needn't upgrade.

> Now that I've solved the keyboard problem, could somebody go back to my
> yesterday's posting with subject "CDE login on Alphas with VNC"
>
> and check my XDMCP configuration and my list of minor (or not so minor)
> problems ?
>
>
> I start the VNC server at boot from /etc/dt/config/Xservers with
>
> :1   Local   local@none    XXX YYY -once -query servername :1

Okay, the '-once' and the -query are the problems. What you need here is:
  :1  LocalVNC1 local@none .../Xvnc -geometry YYY [other VNC options as 
required]
and in your dtlogin resource file (Xconfig on my Solaris system, I don't know 
what it will be on yours):
   *LocalVNC1.terminateServer: true
It may also be useful to do something like:
   *LocalVNC1.environment: VNC=true
so your login script can tell (by looking for $VNC) when you are running 
inside VNC. See the dtlogin manual page for a full list of the resources you 
can use.

This will start the server properly (you don't need the extra stuff done by 
the vncserver script] and will terminate it and restart when you logout.

You may still want to use a script to start Xvnc if the option list is long - 
if the line gets too long in Xservers, it is silently truncated.

Useful options to use for Xvnc would include the font path; use a font server 
if available, so you get exactly the same font set as if you were sitting at 
the console.

This has been tested and confirmed to work on a Solaris system using CDE.

The -query, by the way, should only be used if the server is *not* being 
started from Xservers - it tells the X server (Xvnc) to connect to the named 
XDMCP host to get managed. If you're running through Xservers, it's already 
managed.

Likewise, -once shouldn't be used here - the X display manager should manage 
the starting and terminating of the X server itself.

- -- 

Grant McDorman <[EMAIL PROTECTED]>, Sr. Software Design Consultant
Cedara Software Corp.  <URL:http://www.cedara.com>
  (formerly I.S.G. Technologies Inc.)
Mississauga, Ontario, Canada

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (SunOS)

iD8DBQE+VS5qLVa+EmyjizARAmbIAKCUCKfl6UW7tTR6Zi/SkgzHjaft/ACeJY3k
YwOGQJsKw3yZyGXt0TUusGs=
=p2OA
-----END PGP SIGNATURE-----
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to