<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 31, 2019, at 10:19 AM, Chris Fowler via Ale <<a href="mailto:ale@ale.org" class="">ale@ale.org</a>> wrote:</div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt;" class=""><div data-marker="__QUOTED_TEXT__" class=""><div class="">tmux. Start the tmux session and run the job in a tmux pane. When you get home SSH back to the server and attach to the tmux session. I use this in development so I can occasionally check up on build status via JuiceSSH on Android. <br class=""></div></div></div></div></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">THIS. I was going to be old and mutter something about screen, but tmux is the new hotness. </div><div class=""><br class=""></div><div class="">Just because you’re not setting keepalive does not mean SSH will not intrinsically keep the connection alive or for some uninstrumented reason clamp the session. Or a network hiccup. Or OOMkiller being a whiny bitch. </div><div class=""><br class=""></div><div class="">Literally any number of things can be hanging up that session for you irrespective of your nohup.</div><div class=""><br class=""></div><div class="">Set the keepalive, or use tmux.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">—j</div></body></html>