My assertion that 'vncserver -fg &' would produce the same behavior was incorrect. If I did that, then pressing Enter would stop the job. I had to also close STDIN to make it work correctly. Further, whenever -fg is used, I adopted Martin's method of automatically killing Xvnc, since otherwise, if you did 'vncserver -fg &' followed by 'vncserver -kill', it would generate an error message (the vncserver script, which was still running in the background, was trying to find the PID file, but it no longer existed.)
r4359 should work as advertised. On 3/11/11 6:53 PM, Robert Goley wrote: > You are right about how X exits. If launched from kdm/gdm it closes X > when the window manager exits. When run stand alone using xinit or > similar, it stays running. The whole xstartup file is basically a copy > of how xinit has always worked. Beside my personal reasons for not > changing the default, the best reason to me is that it changes how > TigerVNC works from all previous unix implementations. I know that will > end up biting many more than me. I like the fact that you can change the > behavior if needed with the -fg switch for those that need the different > behavior. > > Robert > > On Mar 11, 2011 7:38 PM, "DRC" <dcomman...@users.sourceforge.net > <mailto:dcomman...@users.sourceforge.net>> wrote: >> If you are using a display manager (gdm, etc.) then it will log you out > if the WM crashes or exits. However, not everyone uses a display > manager. If you are running the X server as a standalone application, > then I think it will remain running if the WM crashes. Maybe I'm wrong, > though. Personally, I find the approach of auto exiting Xvnc more > palatable, but those who want to do that still can. It just won't be the > default. >> >> On Mar 11, 2011, at 3:58 PM, Martin Koegler <mkoeg...@auto.tuwien.ac.at > <mailto:mkoeg...@auto.tuwien.ac.at>> wrote: >> >>> On Fri, Mar 11, 2011 at 02:56:51PM -0500, Robert Goley wrote: >>>> You have been more fortunate then. My users always seem to find >>>> those unknown or unlikely crashes or closes. We have used KDE/GNOME >>>> in the past but they are kind of "heavy" and slow down the VNC >>>> session performance when using it over lower bandwidth connections. >>>> We use windows managers like jwm or openbox + lxpanel to provide a >>>> desktop session similar to Window's RDP sessions with all the >>>> graphical features turned off. This also allows for restricted the >>>> applications that users have access to. Keeps it simpler for them >>>> that way too. >>> >>> It would be interessting to compare this to behaviour of local X >>> display managers: >>> >>> They must kill the X server at some point of time too, regardless if >>> you use a failsafe session or KDE - how do they handle this decision? >>> >>> Regards, >>> Martin Kögler >>> >>> > ------------------------------------------------------------------------------ >>> Colocation vs. Managed Hosting >>> A question and answer guide to determining the best fit >>> for your organization - today and in the future. >>> http://p.sf.net/sfu/internap-sfd2d >>> _______________________________________________ >>> Tigervnc-devel mailing list >>> Tigervnc-devel@lists.sourceforge.net > <mailto:Tigervnc-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/tigervnc-devel > > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > > > > _______________________________________________ > Tigervnc-devel mailing list > Tigervnc-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tigervnc-devel ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
