> -----Original Message----- > From: Lee Allen [mailto:[EMAIL PROTECTED]] > > > A problem looks like this: > > > > > > Sep 9 15:18:41 netfinity inetd: launching: 5900 > > > Sep 9 15:18:41 netfinity inetd: accept: new socket 3 > > > Sep 9 15:18:41 netfinity inetd: pid 24626: exec > /usr/local/bin/Xvnc > > > Sep 9 15:18:41 netfinity inetd: uid: 507 gid: 103 > > > Sep 9 15:18:41 netfinity inetd: groups: 103 100 102 > > > Sep 9 15:18:41 netfinity inetd[24430]: pid 24626: exit status 1 > > > Sep 9 15:18:41 netfinity inetd: pid 24626, exit status 100 > > > > What's process id 24430? > > How manny instances of inetd have you running? > > Just the one. To run inetd in debug mode, I must kill the > inetd daemon, and run it interactively. > > > Is your app working properly without window manager? > > Can it have multiple instances? > > is it the other pid above? > > It works fine without a wm. Yes, it has multiple instances. I think > pid 24626 is the Xvnc process. > > I should point out that this works great the majority of the time. We > may have 5 or 10 sessions running at a time. Only > about one in ten viewer startups fails as described. Then, it takes > about a minute before that client can connect again. (Yes, there is > some new information here, I have done much more testing). > > I am about to do another test to see if only that client is prevented > from connecting during the minute, or are all clients. > But first, I have installed TightVNC 1.2.6, and I will see if I can > still reproduce the problem.
Keep track on the memory in use. It can also be a paging/swapping problem. Have `top` running in a terminal to see the swap usage. It's possible you're at the end of physical memory and the system starts swapping. > > > For your patched Xvnc, you did not have to patch it. There > > are more options to start an app at login. For example create > > a dedicated user and start the app from the ~/.xstartup file > > (this depends on the used window manager). > > What I am really trying to avoid is the xdm login screen. Our > application authenticates the user. I have not been able to > find a way > to start an app without (1) pre-starting all sessions, or (2) > using xdm > with the redundant (in our case) login. An idea is to have inetd call a script that starts the app and then changes into Xvnc. This has some problems to tackle: The app can only start after the Xvnc is started. Because it needs the display to be avialable (and it needs to know which $DISPLAY it gets...) Xvnc must be started as last command by means of an 'exec'-call: `exec Xvnc`. For various reasons, including getting the open file pointers. Now I think of it, I recal kdm or gdm (I don't know which one) to have an option to do an automatic login. Have a look at them to start your app. > > Can you provide any more information on how to do this? Yes, but not better than the above. CBee _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
