question about proposed feature for Xvnc

Lee Allen lee "at"
Mon, 25 Mar 2002 15:12:03 +0000

"Beerse, Corni" <cbeerse "at"> wrote:

When Tony told me about this function, I jumped all over it: It was
something I had been needing without realizing it.  We use vnc in the same
situation he describes: Many users running a single application.  We have
been using Xvnc in -inetd mode, together with XDM, to start the application.
This works, but has some disadvantages:
-    the XDM authentication (login screen) is unnecessary in our situation,
and I have not been able to find a way to avoid it, so it is a considerable
nuisance for the users
-    as is obvious from the many posts on this forum, the initial learning
curve and setup of XDM is daunting for many Xvnc users: it is a more
functionally rich mechanism than most people need

> It is reasonable thinking to use a -startapp but what do you do with the
> options (-broadcast, -query...)?

You omit them.  The whole point is to avoid xdm.

> Do you need a window manager? IF the
> startapp also has subwindows (show me an X11 app which has none), then you
> need the windowmanager to rearange the windows within the vnc screen.

Our particular application has subwindows but puts them where they belong
and sizes them appropriately: the user cannot move them.  We were not using
a window manager under the xdm approach.  Yes, this is a very 'controlled'
application, which also makes it idiot-proof.  It is intended for
unsophisticated users.

> I can think of many more of these questions and to solve them, you end up
> rebuilding your own windowmanager. And now I write this, the app can
> be ~/.vnc/xstartup (even default to it?) to have the same usage as with
> vncserver startup script.
> Hence: make the -startapp disable the xdm options.

Oh, I guess we arrived at the same point, as far as the xdm options.  But
your suggestion to use -startapp with vnc/xstartup is intriguing.  Yes, that
should provide a window manager.

> What do you do once the connection is gone? Just kill the Xvnc? or also
> the started application? (and all it's childs?)

Yes: Immediately after forking, the child process sets its PGID=PID.  The
parent retains the PID.  When Xvnc terminates, it kills everything in the
child's PGID.

Lee Allen
Leadtec Systems, Inc.
To unsubscribe, mail majordomo "at" with the line:
'unsubscribe vnc-list' in the message BODY
See also: