<html>
<head>
<style>
.sw_message P{margin:0px;padding:0px;}
.sw_message {FONT-SIZE: 12pt;FONT-FAMILY:Tahoma,Arial,Helvetica,sans-serif;background:white;}
.sw_message blockquote{margin-left:5px;padding-left:5px;border-left:2px solid #144fae;color: #144fae;}
.sw_message blockquote blockquote{border-left:2px solid #006312;color: #006312;}
.sw_message blockquote blockquote blockquote{border-left:2px solid #8e5656;color: #8e5656;}
.sw_message blockquote blockquote blockquote blockquote{border-left:2px solid #888;color: #888;}
</style>
</head>
<body class="sw_message">
I have used autossh to monitor an ssh tunnel and restart it if necessary.<br><div> </div><div> </div><div id="editor_signature"></div><div>On Wednesday 17/05/2017 at 2:13 pm, Iznogoud wrote: </div><blockquote type="cite">Thanks for this info. you are saying processes will terminate if trying to<br>write to stdout, but would otherwise stay alive if signals were set to be<br>ignored, correct?<br><br><br><blockquote type="cite"> <br> An example of this that I use is a backgrounded ssh port forward: "ssh -L <br> 1234:target.host:22 -N pivot.host &"<br> I've had these last though complete logouts, which I like, until I really <br> want it to terminate and need to run netstat -lnp to find it again.<br> <br></blockquote><br>The last part, about finding them and terminating them, you are looking for the<br>PID that is attached to the socket. I think for your purpose this would work<br>best: 'ps axu | grep ssh | grep 1234'<br><br>But I see your point.<br><br>As a side note, I have not had much luck with non-executing ssh tunnels (-N)<br>staying alive in most cases. I should also say, I am mostly using reverse<br>tunnels (-R).<br><br>_______________________________________________<br>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>tclug-list@mn-linux.org<br><a target="_blank" href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br><br></blockquote><br>
</body></html>