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. > > 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 u...@machine startfluxbox > > you might try > > ssh -nY u...@machine startfluxbox > > 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 u...@machine "export DISPLAY=mymachine:9;xterm;logout" >> >> But both of these have the problem: >> >> ssh u...@machine "export DISPLAY=mymachine:9;startfluxbox;logout" >> ssh u...@machine "export DISPLAY=mymachine:9;exec startfluxbox;logout" >> >> >> Now the "Narrowing It Down" and "Really Strange" part. This works >> just fine: >> >> ssh u...@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 tun...@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/