Sponsored Content
Full Discussion: X Windows display
Top Forums UNIX for Advanced & Expert Users X Windows display Post 302817951 by DGPickett on Thursday 6th of June 2013 04:48:43 PM
Old 06-06-2013
VNC can display any desktop on any host. VNC can remote control windows, MAC or X. In X, Xvnc runs as a daemon on the box providing XServices to write a virtual, in memory desktop that a viewer can see. I usually run one per UNIX box, so any X on that box does not play tcp ping pong on the lan; it is all local.

Some complex X apps then load and run much more quickly. The app writers might have had a local console as X screen, never having to deal with long and latent tcp connections.

To operate the X desktop, you connect with vncviewer, using port 59xx tcp. VNC has many compressions and tricks to allow the desktop to display well even on low bandwidth. If you kill the vncviewer or tcp connection, all the X apps are still connected to Xvnc, awaiting your return on a new viewer connection. Some versions of vnc are free. There are many vnc viewers, like ultravnc and now I use the java tightvnc, so my XP shortcuts look like this:
Code:
C:\WINNT\system32\javaw.exe -jar "C:\Documents and Settings\myid\My Apps\tvnjviewer-2.6\tightvnc-jviewer.jar"  ....

You can set up vnc to allow multiple viewers for mentoring and training. By default, any new viewer disconnects old ones, so you can change locations and pick up where you left off, or fire up a new vncviewer if it hangs.
 

5 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Remote X-Windows "Display" Access

Hi all, I am trying to get XScrabble running on my two FreeBSD boxes "freeserver" and "freework". When I set it up for two "human" players on "freeserver" it asks me for the X Displays to use, eg. ":0.0" so, I try: Human1 :0.0 Human2 freework:0.0 The problem is I get the error:... (1 Reply)
Discussion started by: WIntellect
1 Replies

2. UNIX for Advanced & Expert Users

How to open display from windows to solaris?

How can I telnet from my windows XP machine to my Ultra 60 and run firefox? I am unable to open the display using /usr/openwin/bin/xhost like I do from one Sun machine to another? Thanks (2 Replies)
Discussion started by: ridgeback00
2 Replies

3. Red Hat

Help with exporting DISPLAY from Linux to Windows XP

Hi Experts, I am using Cygwin and Xming server to bring back the display from Linux to a Windows machine. I am following the below steps :- 1. Close down all X Servers 2. Run XMing – XLaunch 3. Select Multiple 4. Select Start no clients 5. Tick No Access Control box 6. Click Finish... (7 Replies)
Discussion started by: oopsalion
7 Replies

4. UNIX and Linux Applications

pass an xpdf display from red hat server to windows ssh workstation

I have a UniVerse database running on a Red Hat EL3 server. If I am on the server console my software can call xpdf giving the name of a target file and it displays very nicely on the console. I have not been able to figure out how to get the display to happen on any of the Windows XP workstations.... (5 Replies)
Discussion started by: dale kelley
5 Replies

5. Solaris

Exporting display to windows machine

hello all, I have been googling alot about my problem and finally thought to post a question. server: SunOS 5.1 64bit pn Sun Netra 240 i need to run an application which shows a gui tool but i believe SunOS cant show the GUI so i need to export the display to my system which is running... (3 Replies)
Discussion started by: wonderwall
3 Replies
vncserver(1)						     Virtual Network Computing						      vncserver(1)

NAME
vncserver - start or stop a VNC server SYNOPSIS
vncserver [:display#] [-name desktop-name] [-geometry widthxheight] [-depth depth] [-pixelformat format] [-fp font-path] [-fg] [-autokill] [Xvnc-options...] vncserver -kill :display# DESCRIPTION
vncserver is used to start a VNC (Virtual Network Computing) desktop. vncserver is a Perl script which simplifies the process of starting an Xvnc server. It runs Xvnc with appropriate options and starts a window manager on the VNC desktop. vncserver can be run with no options at all. In this case it will choose the first available display number (usually :1), start Xvnc with that display number, and start the default window manager in the Xvnc session. You can also specify the display number, in which case vnc- server will attempt to start Xvnc with that display number and exit if the display number is not available. For example: vncserver :13 Editing the file $HOME/.vnc/xstartup allows you to change the applications run at startup (but note that this will not affect an existing VNC session.) OPTIONS
You can get a list of options by passing -h as an option to vncserver. In addition to the options listed below, any unrecognised options will be passed to Xvnc - see the Xvnc man page, or "Xvnc -help", for details. -name desktop-name Each VNC desktop has a name which may be displayed by the viewer. The desktop name defaults to "host:display# (username)", but you can change it with this option. The desktop name option is passed to the xstartup script via the $VNCDESKTOP environment variable, which allows you to run a different set of applications depending on the name of the desktop. -geometry widthxheight Specify the size of the VNC desktop to be created. Default is 1024x768. -depth depth Specify the pixel depth (in bits) of the VNC desktop to be created. Default is 24. Other possible values are 8, 15 and 16 - any- thing else is likely to cause strange behaviour by applications. -pixelformat format Specify pixel format for Xvnc to use (BGRnnn or RGBnnn). The default for depth 8 is BGR233 (meaning the most significant two bits represent blue, the next three green, and the least significant three represent red), the default for depth 16 is RGB565, and the default for depth 24 is RGB888. -cc 3 As an alternative to the default TrueColor visual, this allows you to run an Xvnc server with a PseudoColor visual (i.e. one which uses a color map or palette), which can be useful for running some old X applications which only work on such a display. Values other than 3 (PseudoColor) and 4 (TrueColor) for the -cc option may result in strange behaviour, and PseudoColor desktops must have an 8-bit depth. -kill :display# This kills a VNC desktop previously started with vncserver. It does this by killing the Xvnc process, whose process ID is stored in the file "$HOME/.vnc/host:display#.pid". The -kill option ignores anything preceding the first colon (":") in the display argument. Thus, you can invoke "vncserver -kill $DISPLAY", for example at the end of your xstartup file after a particular application exits. -list Lists running VNC servers. -fp font-path If the vncserver script detects that the X Font Server (XFS) is running, it will attempt to start Xvnc and configure Xvnc to use XFS for font handling. Otherwise, if XFS is not running, the vncserver script will attempt to start Xvnc and allow Xvnc to use its own preferred method of font handling (which may be a hard-coded font path or, on more recent systems, a font catalog.) In any case, if Xvnc fails to start, the vncserver script will then attempt to determine an appropriate X font path for this system and start Xvnc using that font path. The -fp argument allows you to override the above fallback logic and specify a font path for Xvnc to use. -fg Runs Xvnc as a foreground process. This has two effects: (1) The VNC server can be aborted with CTRL-C, and (2) the VNC server will exit as soon as the user logs out of the window manager in the VNC session. This may be necessary when launching TigerVNC from within certain grid computing environments. -autokill Automatically kill Xvnc whenever the xstartup script exits. In most cases, this has the effect of terminating Xvnc when the user logs out of the window manager. FILES
Several VNC-related files are found in the directory $HOME/.vnc: $HOME/.vnc/xstartup A shell script specifying X applications to be run when a VNC desktop is started. If this file does not exist, then vncserver will create a default xstartup script which attempts to launch your chosen window manager. $HOME/.vnc/passwd The VNC password file. $HOME/.vnc/host:display#.log The log file for Xvnc and applications started in xstartup. $HOME/.vnc/host:display#.pid Identifies the Xvnc process ID, used by the -kill option. SEE ALSO
vncviewer(1), vncpasswd(1), vncconfig(1), Xvnc(1) http://www.tigervnc.org AUTHOR
Tristan Richardson, RealVNC Ltd. D. R. Commander VNC was originally developed by the RealVNC team while at Olivetti Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people participated in development, testing and support. TigerVNC 13 Mar 2011 vncserver(1)
All times are GMT -4. The time now is 04:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy