My VNC died


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications My VNC died
# 1  
Old 01-17-2008
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 failed: Protocol not supported"

Any idea why this is happening.

Kind thanks,

Mike
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. What is on Your Mind?

ASUS ROG PG348Q Curved 34" Gaming Monitor Died

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

subversion died after connect port 3699

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

Problem with VNC

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?

pupp's computer died !! :(

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

boot failure-init died

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

WARNING - exit init (PID1) died.

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

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

8. UNIX for Advanced & Expert Users

Many dtexec process that do not died

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

Installation died on the beginning.

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
Login or Register to Ask a Question
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)