1 |
On Sunday 17 Jul 2016 16:20:30 Ralf wrote: |
2 |
> On 07/17/2016 04:02 PM, Mick wrote: |
3 |
> > I am not sure of the correct approach to achieve a prolonged remote |
4 |
> > debugging session through SSH and avoid the SSH session timing out. |
5 |
> > |
6 |
> > This is what I try to achieve: |
7 |
> > |
8 |
> > I login into a router with SSH from my PC. Then I can run certain |
9 |
> > commands to start and monitor a debugging session in the router. |
10 |
> > However, if I leave alone the SSH session, it will soon time out. The |
11 |
> > debugging only runs while the session is live. Exiting the SSH session |
12 |
> > causes all debug output to be lost. |
13 |
> |
14 |
> Take a look at screen or tmux. man screen, man tmux. |
15 |
|
16 |
Thank you Ralph, but detaching the *local* terminal process of SSH does not in |
17 |
any way stop the login session on the router from timing out. |
18 |
|
19 |
|
20 |
> > If I continue to run (router) commands on the terminal, while the |
21 |
> > debugging is running, the SSH time out is postponed. |
22 |
> |
23 |
> you may also want to tweak some timeout options in your sshd_config |
24 |
|
25 |
The router login times out unless some command is fed into the login session a |
26 |
the time. So, I'll need to be able to run commands every so often on the |
27 |
router shell from within my SSH session (without sitting in front of my PC |
28 |
terminal of course). The commands 'watch', or 'at' might do it, but I am not |
29 |
sure if some script is necessary for this. |
30 |
|
31 |
-- |
32 |
Regards, |
33 |
Mick |