<div dir="ltr">Hello Dan,<div><br></div><div>For idea #1, please check out the MOSH_SERVER_NETWORK_TMOUT and MOSH_SERVER_SIGNAL_TMOUT environment variables. These are documented in the mosh-server(1) man page. The feature was released in Mosh 1.2.6 (August 2016) so your mosh-server needs to be at least that new.</div><div><br></div><div>For idea #2, we could certainly try to be more sophisticated than the current behavior, but I think many people deal with this by using mosh to invoke a command like "screen -dr", which automatically cleans up any older mosh session before starting the new one.</div><div><br></div><div>E.g.: mosh user@server -- screen -dr</div><div><br></div><div>Regards,</div><div>Keith</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 18, 2017 at 10:09 PM, Dan Mahoney (Gushi) <span dir="ltr"><<a href="mailto:danm@prime.gushi.org" target="_blank">danm@prime.gushi.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
I'm aware that for every mosh connection (i.e. one each from my laptop,<br>
desktop, and other laptop), I'm going to have a mosh-server connection.<br>
These each have their own ssl key, and they pass a screen session around,<br>
by doing a screen -d -r on whatever system I sit down at.<br>
<br>
Recently, it seems like I had something like 20 mosh-server sessions<br>
running, which cropped up at various times as I did updates on my various<br>
systems, and then ssh'd back in.<br>
<br>
I'm aware that mosh cannot possibly know when a system has been rebooted,<br>
so can't know when to kill a server session.<br>
<br>
That said, one useful idea would be killing any session that hasn't been<br>
"used" in over some period of time (say, a week?). This could be done by<br>
giving mosh-server some kind of idle timeout -- or by making this<br>
queryable somehow, so that a server-side crontab could clear these out.<br>
<br>
A second (more complicated) idea would be -- assume that I'll only ever<br>
connect once from a given machine -- and allow me to "kick" any other<br>
connections from my existing hostname. Is this possible? It would<br>
require mosh to know the hostname of the client machine and somehow be<br>
able to compare that on servers. (Obviously this is less workable when<br>
your hostname is dynamic, assigned via your DHCP server or based on your<br>
RDNS).<br>
<br>
-Dan<br>
<br>
--<br>
<br>
--------Dan Mahoney--------<br>
Techie, Sysadmin, WebGeek<br>
Gushi on efnet/undernet IRC<br>
ICQ: 13735144 AIM: LarpGM (Farewell, AIM!)<br>
Site: <a href="http://www.gushi.org" rel="noreferrer" target="_blank">http://www.gushi.org</a><br>
---------------------------<br>
<br>
______________________________<wbr>_________________<br>
mosh-users mailing list<br>
<a href="mailto:mosh-users@mit.edu" target="_blank">mosh-users@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/mosh-users" rel="noreferrer" target="_blank">http://mailman.mit.edu/mailman<wbr>/listinfo/mosh-users</a><br>
</blockquote></div><br></div></div>