10 More Discussions You Might Find Interesting
1. Red Hat
Hello everyone,
This is my last resort.
I have searched the internet everywhere using different search engines as well.
I am using Redhat 7 where I activated a vncserver (since it comes pre-installed).
using the following service:
Description=Remote desktop service (VNC)... (0 Replies)
Discussion started by: Deyan Broekman
0 Replies
2. Red Hat
I'm trying to use VNC from my desktop to connect to a RedHat (RHEL6) Server. I connect but the screen is black. It I go into the Data Centre the screen is unlocked and all is okay there. I can connect no problem to other Desktops & Servers. Is there a setting maybe or can anybody suggest another... (6 Replies)
Discussion started by: itwex
6 Replies
3. Fedora
Hi,
I set-up my VNC Server on a Fedora 13 and I have a client on windows.
I can access the Fedora PC but when I move the mouse and click on folders, I do not see the Fedora Desktop updating (I don't see the things that I am doing in my client on the Fedora PC)
Then, when I do something on... (0 Replies)
Discussion started by: h0ujun
0 Replies
4. UNIX for Dummies Questions & Answers
hi guys
Suse 10 SP2
Security guys run an app called Nessus for vulnerabilities and they found this one on my linux
VNC Server Unauthenticated Access
and I really don't know what they mean...
I can update vnc on these servers but there is not guarantee this will fix the issue and the... (2 Replies)
Discussion started by: kopper
2 Replies
5. Red Hat
Dear all,
I am using Fedora15 kde
I have installed Real vnc (server & viewer)
real vnc Viewer is working fine - i like this.
real vnc server has License period expired problem (i dont know how to add)
I have x11vnc server (Desktop sharing) installed - Its working fine too.
I... (2 Replies)
Discussion started by: linuxadmin
2 Replies
6. Solaris
I 'm unable to start vnc server, i get following error in the log file
Fatal server error:
could not open default font 'fixed'
xsetroot: unable to open display 'essapl020-u009:0'
twm: unable to open display "essapl020-u009:0"
xterm Xt error: Can't open display: essapl020-u009:0... (0 Replies)
Discussion started by: fugitive
0 Replies
7. Linux
I am running Startcom linux ES5 . When i bring up the VNC server and login to the machine running a vnc client , I only get the real basic x-windows session and a term window. how can i get it to bring up the real linux desktop on all sessions?
Frank (4 Replies)
Discussion started by: frankkahle
4 Replies
8. Solaris
hey. i have been installing the VNC server from the solaris Companion cd under solaris 8 SPARC,
when i try to open the vncserver i get: Xvnc is not in your PATH, how do i add it to the PATH ? and how do i install it if i need to do that,
thx (0 Replies)
Discussion started by: mads-nielsen
0 Replies
9. AIX
Hello
I need to be able to take control of the native X server ( :0.0 ) on AIX5.3 workstations via VNC to be able to assist users...seeing what they are doing is much better than them telling me what they are doing.
I know that this can be done on linux so it should doable on AIX.
On linux... (0 Replies)
Discussion started by: art
0 Replies
10. Linux
Hi All,
I'm running RH 9.0 on a PII box with 160MB RAM. Just downloaded RealVNC X86 Linux (version 3.3.7). How can I get the HTTP listening port up ?
Thanks,
KENT (6 Replies)
Discussion started by: kxchen_home
6 Replies
LEARN ABOUT CENTOS
vncserver
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)