On 03/16/2011 09:59 PM, Eric Stadtherr wrote:
On Wed, 16 Mar 2011 15:50:53 -0500, DRC wrote:
http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases
-- Reverts default behavior of vncserver but adds a 'vncserver
-autokill' option that will automatically kill Xvnc whenever xstartup exits.
On 03/16/2011 09:50 PM, DRC wrote:
http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases
-- Reverts default behavior of vncserver but adds a 'vncserver
-autokill' option that will automatically kill Xvnc whenever xstartup exits.
Builds fine, runs fine (Linux 64). No comments from me on
On Fri, Mar 18, 2011 at 03:28:26PM +0100, Sebastiaan Breedveld wrote:
On 03/16/2011 09:50 PM, DRC wrote:
http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases
Just for information, how did you build Windows stuff? Via mingw or
msvc?
I tested the 32bit build and it seems fine for me. In
http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases
-- Reverts default behavior of vncserver but adds a 'vncserver
-autokill' option that will automatically kill Xvnc whenever xstartup exits.
--
Colocation vs.
On Wed, 16 Mar 2011 15:50:53 -0500, DRC wrote:
http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases [1]
--
Reverts default behavior of vncserver but adds a 'vncserver
-autokill'
option that will automatically kill Xvnc whenever xstartup exits.
How
does this interact with the
-once shuts down Xvnc after the first VNC connection has disconnected.
It only works when Xvnc is run from inet.d (it's designed to be used to
launch Xvnc on demand as a connection comes in.) -autokill is a
fundamentally different feature. -autokill is a function of the
vncserver startup script,
Just to throw my 2 cents in as well... I would prefer this behavior
be reverted as well. I know it will end up causing us problems if
for no other reason than window managers crash and we don't want
everything else in our session to be taken down with them
It seems that the -fg was implemented differently than expected:
diff between old and new
-system("$vncUserDir/xstartup " .
quotedString($desktopLog) . " 21 ");
+if ($opt{'-fg'}) {
+ system("$vncUserDir/xstartup " .
quotedString($desktopLog) . " 21");
No, it was intentional. I was implementing both the -fg functionality and
Martin's suggestion to change the default behavior. Adam and Robert objected to
the change in default behavior. I am seeking clarification about the objections.
On Mar 11, 2011, at 8:43 AM, Sebastiaan Breedveld
On Fri, Mar 11, 2011 at 08:41:02AM -0600, DRC wrote:
Just so I fully understand the issue, what would you normally do if the WM
crashes? Is there a reasonable way to recover in that case?
When WM crashes then applications which are started for example from
xstartup script are not terminated
Restart the window manager and not lose any of the work we were in
the middle of.
Typically, it would be the following commands in an xterm or
similar:
openbox (though this could be other WMs as well)
disown
exit
On 03/11/2011 09:41
On Fri, Mar 11, 2011 at 04:05:00PM +0100, Adam Tkac wrote:
On Fri, Mar 11, 2011 at 08:41:02AM -0600, DRC wrote:
Just so I fully understand the issue, what would you normally do if the WM
crashes? Is there a reasonable way to recover in that case?
When WM crashes then applications which
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
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
My take on it is that we shouldn't be dictating someone's workflow. If this
modification prevents people from using TigerVNC in the manner they want to use
it, then we should revert it, because like I said, you can accomplish exactly
the same thing with vncserver -fg
I will make the
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,
16 matches
Mail list logo
