<div class="gmail_quote">On Thu, Feb 4, 2010 at 11:15, Erik Iverson <span dir="ltr"><<a href="mailto:eriki@ccbr.umn.edu">eriki@ccbr.umn.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On my desk, I have a thin client that is configured to connect to an ancient version of Solaris, and I did not deem it worth my time to try to get openbox to compile on this machine. So I compiled it on a comparatively new Linux server installation, and have as the last line of my .xinitrc:<br>
<br>
ssh -Y linux-server openbox-session<br>
<br>
(the -Y option enables X forwarding on this version of ssh)<br>
<br>
So, of course any programs that start over the X-forwarded ssh connection will have to be terminated before ssh returns, including anything I start up in autostart.sh.<br>
<br>
I will just have to come up with a script that will kill all X-forwarded apps before attempting to exit, or just do it myself. That's probably not too bad since the list of applications that will be X-forwarded are pretty predictable in my case (the dock apps, panel stuff, etc.).<br>
</blockquote><div><br></div><div> What I do in a similar case is the following:</div><div> </div><div>> ssh host "$SESSION; kill \$PPID"</div><div><br></div><div>where SESSION is openbox, or gnome, or whatever. This means that after the SESSION exits, the parent process of the remote session (the user-specific sshd fork) gets killed, killing ssh. This is exactly what happens in a normal X session approach: once the session-controlling process terminates, the X server terminates, forcibly killing anything else that was attached to it. Just in this case, it's the ssh-tunneled X environment.</div>
<div><br></div><div>Note the backslash, to ensure that PPID is interpolated on the other machine, not the local one.</div><div><br></div></div>-- <br>Jeremy Nickurak -= Email/XMPP: <a href="mailto:jeremy@nickurak.ca">jeremy@nickurak.ca</a> =-<br>
<br>