11-12-2008
I have not messed with vnc for years. There is a ~/.vncrc file and /etc/vnc.conf file as well. Those control user-level and system level settings. I do not recall a concurrent client limit setting. Check your docset.
My real question is - are you really sure you need 500?
10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
Hello!
Im running tight VNC on Red Hat Enterprise Linux 4.0.
How can I increase the number of X clients that I can run
in a VNC session?I need to run aproximately 500 programs in one VNC session,
but at this time I can only 236 -> i've tryed to launch 250 xclock's in background
and when it... (0 Replies)
Discussion started by: karpoand
0 Replies
2. Programming
Hi all,
I'm currently learning xlib and I've encountered a bizarre mistake: function calls such as XDrawPoint, XDrawLine, etc., don't seem to work; a blank window with nothing in is appears. I believe this has something to do with the window manager I use, fluxbox.
After checking the code and... (0 Replies)
Discussion started by: hydronium
0 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am handling user issues in my team. Users have their Unix session running on Citrix MFU.
Recently, I was suppose to address a user issue which is as below:
Gets the below error when tries to open nedit:
Xlib: connection to ":165.0" refused by server
Xlib: Client is not... (1 Reply)
Discussion started by: mspatil0037
1 Replies
4. Programming
Hey guys!
First of all english is not my main language so sorry for any english mistakes.
Second im a total beginner in programming, still i have a school work to do and i found a problem. Probably something easy to solve but it's driving me crazy.
So i created a struct, that holds 4 ints:
... (1 Reply)
Discussion started by: Spiritvs
1 Replies
5. Homework & Coursework Questions
Hey guys!
First of all english is not my main language so sorry for any english mistakes.
Im from Portugal!
1. The problem statement, all variables and given/known data:
Im having a problema creating and array of structs for a work i need to do. (xLib)
2. Relevant commands, code,... (1 Reply)
Discussion started by: Spiritvs
1 Replies
6. UNIX for Advanced & Expert Users
Two simple questions related to the following puzzling behaviour:
I have the following line of code:
const KeyCode kc = XKeysymToKeycode(_display_p, ks);
where _display_p is a valid Display* returned from XOpenDisplay() and ks has the value 103 (which was returned by XStringToKeysym(),... (2 Replies)
Discussion started by: N7DR
2 Replies
7. Programming
hey,
Im new to the linux world. Lately, I have tried to create a glx window with xlib, making it a popup window(fullscreen) so I set override_redirect to true. Im happy with the removed borders, but apparantly, the application doesnt show up in the left bar in ubuntu, neither when I press alt... (4 Replies)
Discussion started by: thedardanius
4 Replies
8. Programming
Hello,
i'm trying to show the Image of an monochrome webcam in an xlib-Window.
initializing of the window:
if (NULL == ((*XWindow)->display = XOpenDisplay(NULL))) APPLICATION_Set_Error(V4LCamera->Application, XWINDOW, "failed to open display", 123, -1, APPLICATION_ERROR_MESSAGE);
... (1 Reply)
Discussion started by: mirrowwinger
1 Replies
9. Programming
Hello,
I just try to get the control of a Window by searching his name. I curretly do that :
Window CMD::window_from_name_search(Display *display, Window current, char const *needle)
{
Window retval, root, parent, *children;
unsigned children_count;
char *name = NULL;
... (0 Replies)
Discussion started by: Loustak
0 Replies
10. UNIX for Advanced & Expert Users
Hello. I used to have Pango compiled, however it did not have X support, only Freetype support. Since gtk requires pangoX to be compiled, I went to compile it with Xsupport.
I had to issue a ./configure --prefix=/media/34GB/Arquivos-de-Programas-Linux/PangoX-1.8.2/... (1 Reply)
Discussion started by: colt
1 Replies
LEARN ABOUT DEBIAN
vncpasswd
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)