Re: Restore Alt-Ctl-Backspace As Server Kill

[Tim Daneliuk <tundra at tundraware dot com>]

Tim Daneliuk wrote:
> Mark J. Reed wrote:
>> I don't use it, but "startfluxbox" sounds like something that kicks of
>> fluxbox and then exits (vs xterm which stays around).   Could that be
>> the problem?
> 
> Likely true.

That is, indeed what it was .. at least in some form.  The 
fix turned out to be to configure fluxbox to kickoff an xterm
when *it* started.  I am still unclear why this is happening.
When a wm is kicked off, it has to run in background.  ISTM
that this should be enough to keep the X session up ... it's
not for some reason.  It seems that X specifically wants to
be attached to some kind of terminal/pseudoterminal
to stick around, notwithstanding the use of the -n option,
which seemed to make no difference.


> 
>> Also, if you're using ssh, why not use ssh forwarding instead of
>> sending the X traffic back over a separate, unencrypted connection?
>> And you don't need to logout explicitly; terminating the shell does
>> the same thing.
>>
>> ssh -Y user@machine startfluxbox
>>
>> you might try
>>
>> ssh -nY user@machine startfluxbox

Neither of these solved the problem (not surprising).  However,
introducing X forwarding *really* slowed startup down - from about
2-3 seconds to about 10-15 seconds.  It looks like this is all
related to setting up the encrypted channel, because once it's 
setup, system interaction is at subjectively normal speed.

>>
>> to prevent standard input from causing a problem...
> 
> D'oh.  That *is* a much better way to do this.  I shall look into
> this as I am able ...
> 
> Thanks!
> 
> 
>>
>> On Tue, Feb 3, 2009 at 2:48 PM, Tim Daneliuk wrote:
>>>  ssh user@machine "export DISPLAY=mymachine:9;xterm;logout"
>>>
>>> But both of these have the problem:
>>>
>>>  ssh user@machine "export DISPLAY=mymachine:9;startfluxbox;logout"
>>>  ssh user@machine "export DISPLAY=mymachine:9;exec startfluxbox;logout"
>>>
>>>
>>> Now the "Narrowing It Down" and "Really Strange" part.  This works
>>> just fine:
>>>
>>>  ssh user@machine "export DISPLAY=mymachine:9;exec fluxbox;logout"
>>>
>>> It seems that something (I have not figured out just what yet)
>>> about the default fluxbox startup script (on FreeBSD 6-STABLE in this
>>> case) is interacting with the cygwin X server and killing it.
>>>
>>> Oiy, my head ...
> 
> 


-- 
----------------------------------------------------------------------------
Tim Daneliuk     tundra@tundraware.com
PGP Key:         http://www.tundraware.com/PGP/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/