Sponsored Content
Full Discussion: vnc Issue
Operating Systems Solaris vnc Issue Post 302777675 by Junaid Subhani on Friday 8th of March 2013 09:07:27 AM
Old 03-08-2013
Hi

I did enable vncserver by the command( I meant installation by that.)
I am able to use VNC client on my Windows machines to login to my solaris server and view its GUI.

The problem starts here!

I login using VNC into my server.
I open Terminal window on Solaris and type a command like prstat -a . I can see its live output.

THEN I close my VNC window.

I again login to my Solaris machines and find that the terminal window is still open but there is nothing shown in it . Just the usual :

root@server#

Why cant I see my previous work ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Vnc

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

2. Solaris

Is there something like vnc for solaris?

my desktop is a linux box, and I was wondering if there was a way to leverage X11/associated applications on a v440 remotely... like "Sun Update Connection"...thanks, manny (4 Replies)
Discussion started by: mr_manny
4 Replies

3. UNIX and Linux Applications

My VNC died

Greetings all, I'm on a solaris 9 system with vnc-4.1.2 installed. I had a connection to a vnc server that suddenly started sapping up cpu cycles - getting up around 13%. I killed the server instance, and now when I try to start a new server, i get the following message: "vncserver: socket... (0 Replies)
Discussion started by: mike_q
0 Replies

4. Linux

VNC/Fedora7 issue

Hi, This has been extremely frustrating, and I need help figuring this one out! I am running Fedora 7 on computer A, and am VNCing into it from my Mac using Chicken of the VNC. For Sarah, everything works fine. However for Bob, the toolbar along the top is missing and every... (0 Replies)
Discussion started by: user23
0 Replies

5. Solaris

VNC as only 1 user issue

Our current VNC setup is for only 1 user login, but this login can not access a few of the programs that I need. How can I add additional logins to VNC? I have only been able to find the logs in .vnc and the usr/bin scripts. (1 Reply)
Discussion started by: gcad76
1 Replies

6. Solaris

VNC issue on solaris10

M running solaris 10 u8 my vncserver is running on :0 .. and when i try to connect it through tight vncview i can see just see the screen .. with no terminal .. what could be the issue for it ? and what i need to check for it ? (2 Replies)
Discussion started by: fugitive
2 Replies

7. Solaris

is x11 and vnc different?

is x11 and vnc different? to my knowledge these are used to provide graphical interface to remote machines for the user who would be sitting some where else. i guess i understood the concept correctly? if not please correct me.. ---------- Post updated at 09:20 AM ---------- Previous update... (3 Replies)
Discussion started by: chidori
3 Replies

8. UNIX and Linux Applications

VNC trouble

I have been having issues with VNC. I have been gettining a lot of errors but mostly gray screens and some black screens. I think this may also be a gnome error. I know that the xstartup file is the file to look at. > more ~/.vnc/xstartup #!/bin/sh && xrdb $HOME/.Xresources xsetroot -solid... (0 Replies)
Discussion started by: bitlord
0 Replies

9. Solaris

vnc issue after reboot

Hi , Everytime after reboot when user tries to start vnc below error is thrown $ vncserver :5 Couldn't start Xvnc; trying default font path. Please set correct fontPath in the vncserver script. Couldn't start Xvnc process. _XSERVTransSocketCreateListener: failed to bind listener... (7 Replies)
Discussion started by: chidori
7 Replies

10. Linux

Open vnc:0

Hi, Is there a way to open vnc:0 on redhat? Thanks (1 Reply)
Discussion started by: Somename
1 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] [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 some X applications to be displayed in 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 as that display, and run a couple of basic applications to get you started. You can also specify the display number, in which case it will use that number if it is available and exit if not, eg: 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 desktop). OPTIONS
You can get a list of options by giving -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 desktop has a name which may be displayed by the viewer. It defaults to "host:display# (username)" but you can change it with this option. It is passed in to the xstartup script via the $VNCDESKTOP environment variable, allowing you to run a different set of applications according to the name of the desktop. -geometry widthxheight Specify the size of the desktop to be created. Default is 1024x768. Can be specified as an array or scalar for geometry. -depth depth Specify the pixel depth in bits of the desktop to be created. Default is 16, other possible values are 8, 15 and 24 - anything else is likely to cause strange behaviour by applications. -pixelformat format Specify pixel format for server 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 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 colour 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 be 8 bits deep. -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". It actually ignores anything preceding a ":" in its argument. This can be useful so you can write "vncserver -kill $DISPLAY", for example at the end of your xstartup file after a particular application exits. 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 it doesn't exist, vncserver will create a new one which runs a couple of basic applications. $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.realvnc.com AUTHOR
Tristan Richardson, RealVNC Ltd. VNC was originally developed by the RealVNC team while at Olivetti Research Ltd / AT&T Laboratories Cambridge. It is now being maintained by RealVNC Ltd. See http://www.realvnc.com for details. RealVNC Ltd 03 Mar 2005 vncserver(1)
All times are GMT -4. The time now is 11:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy