Depending on the RedHat (or clone) version, you'll need to install the vnc-server or tigervnc-server package, or similar, run vncpasswd, then start the server with vncserver :<display>.
Please provide the output of
and some more details on what you're trying to do.
Hi !
Is there somebody who is able to connect a VNC session via serial cable ?
There is a hint on the VNC homepage that it is possible to configure that.
But how?
thanks joerg (2 Replies)
Anyone know of a site where I can download a copy (non-evaluation copy and preferably free. ;) nods to Neo's post in UNIX Operating System thread) of VNC for RedHat 8? Thanks in advance. (7 Replies)
Hi,
I would like to install VNC on my Solaris 6/10 x86 machine. Can someone walk me thru it step by step? I'm very new to Solaris and I would like to get this running ASAP for school so I can VNC into it and use it remotely. I have serached online but the information is so abundant. I don't know... (1 Reply)
First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting.
First, this is what's running:
This is the error when jobs are run or the... (0 Replies)
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)
Hi Friends,
Every I try to open a vi window vim help.txt automatically opens evertime.
After doing ZZ or :q! also the same page opens automatically.
How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue.
Thanks... (1 Reply)
Hi Friends,
Every I try to open a vi window, vim help.txt automatically opens evertime.
After doing ZZ or :q! also the same page opens automatically.
How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue.
Thanks... (3 Replies)
Discussion started by: sudiptabhaskar
3 Replies
LEARN ABOUT DEBIAN
vncserver
vncserver(1) TightVNC vncserver(1)NAME
vncserver - a wrapper to launch an X server for VNC.
SYNOPSIS
vncserver [:display] [-geometry widthxheight] [-depth depth] [-pixelformat rgbNNN|bgrNNN] [-name desktop-name] [Xvnc-options...]
vncserver -kill :display
vncserver -help
DESCRIPTION
vncserver is a wrapper script for Xvnc, the free X server for VNC (Virtual Network Computing). It provides all capabilities of a standard X
server, but does not connect to a display for itself. Instead, Xvnc creates a virtual desktop you can view or control remotely using a VNC
viewer.
OPTIONS
You can add Xvnc options at the command line. They will be added to the invocation of Xvnc without changes. The options provided by the
vncserver itself are as follows:
:display
The display number to use. If omitted, the next free display number is used.
-geometry widthxheight
Set desktop width and height.
-depth depth
Set the colour depth of the visual to provide, in bits per pixel. Must be a value between 8 and 32.
-pixelformat rgbNNN|bgrNNN
Set colour format for pixels representation. The viewer can do the conversion to any other pixel format, but it is faster if the
depth and pixel format of the server is the same as the equivalent values on the viewer display.
-name string
This specifies the name of the desktop.
-kill :display
Stops the session running on the specified display.
-help Prints a short usage notice to stderr.
EXAMPLES
vncserver
Invokes Xvnc on the next available display and with suitable defaults.
vncserver :1
Invokes Xvnc on display :1.
vncserver -geometry 800x600 -depth 16 :1
Invokes Xvnc on display :1 with desktop size of 800x600 pixels and color depth of 16 bits per pixel.
vncserver -kill :1
Shuts down Xvnc server on display :1.
SEE ALSO Xvnc(1), vncviewer(1), vncpasswd(1), vncconnect(1)AUTHORS
Original VNC was developed in AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people
participated in development, testing and support.
Man page authors:
Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>,
Tim Waugh <twaugh@redhat.com>,
Constantin Kaplinsky <const@tightvnc.com>
August 2006 vncserver(1)