My beef is that Xvnc behaves much different than other X servers in how it
handles the startup script. Most X servers will read the .xinitrc file or
whatever startup file is specified and exit once the script exits. This
allows you to run the window manager (whether it's mwm, twm, CDE, VUE/RX,
GNOME, KDE, etc...) in the foreground (i.e. without an &) as the last
command in the startup script. That way once you exit the window manager,
the script exits, and the X server knows it's time to shutdown.
Xvnc just runs the script and then continues running until you kill the
actual server. This is obviously the case since the window manager in the
xstartup file is run in the background (the xstartup file will complete
almost immediately) and the session stays running.
I haven't tried using Xvnc in a query mode, so I can't comment on how that
works. The only odd thing I've noticed with my setup is that every once in a
while (twice a month for 200+ daily users), I get a call to clean up a
session. The symptom is a grey screen (the Xvnc server is running, but no
clients are running) and the solution is simply to kill the Xvnc process. I
haven't been able to track down why all the user's X clients die, but the X
server stays running. It's a real minor nuisance considering that VNC saved
me $40,000 in Windows X server licenses. I plan on adding one extra check in
my slightly modified vncserver script to check for this case and fix it
automatically.
--
Steve Waltner
LSI Logic
> ----------
> From: [EMAIL PROTECTED]
> Reply To: [EMAIL PROTECTED]
> Sent: Monday, March 12, 2001 10:01 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Solaris 2.7 CDE issues
>
> Thanks Steve,
>
> Killing the server is not really appropriate in all scenarios especially
> in xdm environments. After a logout Xvnc should restart (reinitialize)
> and send out a XDMCP request/query again. The problem I'm having is an X
> hang where none of the apps seem to be exiting (they may exit, but after
> I've lost my patience). Perhaps I need to patch CDE. Have you had the
> same problem?
>
> Tom
>
> On Fri, 9 Mar 2001, Waltner, Steve wrote:
>
> > Here is my ~/.vnc/xstartup file that starts, and more importantly
> > kills CDE inside VNC when the user hits the CDE exit button. I really
> wish
> > Xvnc would sense when the xstartup file exited and cleanly exit like the
> > normal X server does when the users .xinitrc file exits so that I
> wouldn't
> > need that vncserver -kill command at the end of the script.
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
