Sponsored Content
Full Discussion: VNC issue on solaris10
Operating Systems Solaris VNC issue on solaris10 Post 302487163 by upengan78 on Tuesday 11th of January 2011 02:56:34 PM
Old 01-11-2011
Do you notice this issue with tightvncviewer only ?

Is your ~/.vnc/xstartup correctly configured?
 

10 More Discussions You Might Find Interesting

1. 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

2. Shell Programming and Scripting

portability issue linux(2.6) solaris10

the following simple scripts work fine on linux but fail on solaris: #!/bin/bash eval /usr/bin/time -f \'bt=\"%U + %S\"\' ./JUNK >> ./LOG 2>&1 cp ./LOG ./LOG_joe LC_joe=`cat ./LOG | wc -l` LC_joe=`echo $LC_joe-1|bc` tail -1 ./LOG > ./tmp head -$LC_joe ./LOG_joe > ./LOG rm ./LOG_joe ... (1 Reply)
Discussion started by: joepareti
1 Replies

3. Solaris

Solaris10

Hi All How can we verify if any of the parameters we have change in Solaris10 after reboot. Like is there any command? Please advice Thanks (3 Replies)
Discussion started by: imran721
3 Replies

4. Solaris

Memory issue on solaris10 box

my system has 128G of installed memory. top, vmstat shows the system has just over 10G of free memory on the system. but as per prstat o/p the usage is just 50-55G is there anyway i can find which process/zone is using more memory ? System has 3 zones and all running application servers. ... (1 Reply)
Discussion started by: fugitive
1 Replies

5. Solaris

/tmp issue on solaris10 box

I have a T5240 server with following swap configuration $ grep tmp /etc/vfstab swap - /tmp tmpfs - yes - $ swap -l swapfile dev swaplo blocks free /dev/swap 4294967295,4294967295 16 213909472 213909472 ... (4 Replies)
Discussion started by: fugitive
4 Replies

6. Solaris

Swap issue on a Solaris10 box

One of our system is running 3 oracle db instances. And as per prstat o/p the system is approximately using 78G of swap memory # prstat -J -n 2,15 PROJID NPROC SWAP RSS MEMORY TIME CPU PROJECT 4038 557 31G 29G 22% 113:23:43 10% proj1 4036 466 20G 19G... (2 Replies)
Discussion started by: fugitive
2 Replies

7. 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

8. Solaris

Veritas I/O fencing issue on Solaris10

I have 2 clusters running on solaris10 servers. VCS is working fine but when i configure I/O fencing with co-ordinated disks only one node have the keys on the disks at time where as both the nodes shuld have keys there what could be the reason for this ? like in the following o/p only Node2's... (0 Replies)
Discussion started by: fugitive
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. Solaris

vnc Issue

Dear all, I recently installed did VNC configuration on a Solaris Server. I am using VNC E4 2 7 as my Windows client. The issue is that every time I log into my machine and use terminal ( a few commands like df -h or any other command and then close VNC ( windows). When I log back in ,... (9 Replies)
Discussion started by: Junaid Subhani
9 Replies
vncpasswd(1)                                                         TightVNC                                                         vncpasswd(1)

NAME
vncpasswd - set passwords for VNC server SYNOPSIS
vncpasswd [file] vncpasswd -t vncpasswd -f DESCRIPTION
The vncpasswd utility should be used to create and change passwords for the TightVNC server authentication. Xvnc uses such passwords when started with the -rfbauth command-line option (or when started from the vncserver script). vncpasswd allows to enter either one or two passwords. The first password is the primary one, the second password can be used for view-only authentication. Xvnc will restrict mouse and keyboard input from clients who authenticated with the view-only password. The vncpasswd util- ity asks interactively if it should set the second password. The password file name defaults to $HOME/.vnc/passwd unless the -t command-line option was used (see the OPTIONS section below). The $HOME/.vnc/ directory will be created if it does not exist. Each password has to be longer than five characters (unless the -f command-line option was used, see its description below). Only the first eight characters are significant. If the primary password is too short, the program will abort. If the view-only password is too short, then only the primary password will be saved. Unless a file name was provided in the command-line explicitly, this utility may perform certain sanity checks to prevent writing a pass- word file into some hazardous place. If at least one password was saved successfully, vncpasswd will exit with status code 0. Otherwise the returned status code will be set to 1. OPTIONS
-t Write passwords into /tmp/$USER-vnc/passwd, creating the /tmp/$USER-vnc/ directory if it does not exist, and checking the permis- sions on that directory (the mode must be 700). This option can help to improve security when your home partition may be shared via network (e.g. when using NFS). -f Filter mode. Read plain-text passwords from stdin, write encrypted versions to stdout. One or two passwords (full-control and view- only) can be supplied in the input stream, newline terminates a password. Note that in the filter mode, short or even empty pass- words will be silently accepted. SEE ALSO
vncserver(1), Xvnc(1), vncviewer(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 vncpasswd(1)
All times are GMT -4. The time now is 08:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy