9 More Discussions You Might Find Interesting
1. What is on Your Mind?
Oh Boy,
Sad News.
My amazing ASUS ROG Swift PG348Q 34" Gaming Monitor has just died.
I'm pretty sure the problem is with the electronic on/off switch, but none-the-less, it's dead.
Purchased on 10 January 2017, the warranty card say it's under 3 year warranty, and I still have the... (10 Replies)
Discussion started by: Neo
10 Replies
2. HP-UX
Hi,
I am trying to setup subversion on hpux 11.11, the svnserve process can be started and the repos have been created, but every we connect to the svn via port 3699 the svnserver will died.
how can i troubleshoot this issue? there is not error from the syslog file. (0 Replies)
Discussion started by: robertngo
0 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I have vncserver installed on Sun Solaris 8. The xstartup file looks like:
#!/bin/sh
&& xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
/usr/dt/bin/dtwm &
I have installed VNC on /usr/local/bin. When I try to... (0 Replies)
Discussion started by: naw_deepak
0 Replies
4. What is on Your Mind?
so my windows xp box has died. trust me, if i didnt game so much id be using solaris or linux but they dont make games for them :( anyway, i've got a really beat up old linux laptop that i'm using now. it runs well it just can't handle most of todays web pages. gmail is awful on this thing!! i wish... (4 Replies)
Discussion started by: pupp
4 Replies
5. HP-UX
Hello.
system fails on reboot this AM.
received message about not possible for kernel to find process that caused crash.
system does memory dump succesfully, then tries to boot again.
looking further at messages during this time, i'm getting 'init died with return value 256'...system panic... (12 Replies)
Discussion started by: mrviking
12 Replies
6. UNIX for Dummies Questions & Answers
Hi,
Today, on one of my SCO machines, i was getting the following:
PANIC : exit cannot exec /etc/init (PID1).
I used two floppy boot/root disks to boot from floppy.
I followed the procedures to restore the files:
/usr/lib/libc.so.1 and /etc/init.
When I reached the part of making... (6 Replies)
Discussion started by: BAM
6 Replies
7. UNIX for Dummies Questions & Answers
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)
Discussion started by: google
7 Replies
8. UNIX for Advanced & Expert Users
Hi,
I have a problem on CDE 1.4 Solaris 8.
It looks like each time I lock the screen, the dtexec that invoke
the dtscreen (that is o.k.) do not died after it done his job and it stay in the system and cause many zombie.
Any suggestions?
Thanks,
Itay. (3 Replies)
Discussion started by: itayst
3 Replies
9. UNIX for Dummies Questions & Answers
Hi, everyone. I tried to install red hat 8.0 on this computer ( CPU: Intel PIII 866, Memory 128 M, HD: 6.4G MATROX, Vedio card: RIVA TNT 16M), but the process always stuck. And the CD-ROM stopped and the light turned of, the HardDrive's light still on. I waited for almost one hour, but nothing... (5 Replies)
Discussion started by: HOUSCOUS
5 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)