If there is still no response, the SSH connection will be disconnected.Performance-snapshot Command Line Analysis hotspots Command Line Analysis anomaly-detection Command Line Analysis threading Command Line Analysis memory-consumption Command Line Analysis hpc-performance Command Line Analysis uarch-exploration Command Line Analysis memory-access Command Line Analysis tsx-exploration Command Line Analysis tsx-hotspots Command Line Analysis sgx-hotspots Command Line Analysis gpu-hotspots Command Line Analysis gpu-offload Command Line Analysis graphics-rendering Command Line Analysis fpga-interaction Command Line Analysis io Command Line Analysis system-overview Command Line Analysis platform-profiler Command Line Analysis runsa/runss Custom Command Line Analysis Configure Analysis Options from Command Line If there is still no response from the client, it will send another alive message at 600 seconds.
If there is no response from the client, it will again send an alive message at 400 seconds. Set the parameters ClientAliveInterval and ClientAliveCountMax to the desired values.įor example, ClientAliveInterval=200 and ClientAliveCountMax=3 means that the server will send an alive message after 200 seconds.Open the sshd config file located at /etc/ssh/sshd_config.Set the parameter in the config file. For example:Įcho "ServerAliveInterval 600" > ~/.ssh/config.
Create the ssh config file (if it does not exist):.When connecting to a server, use the -o option: ssh -o ServerAliveInterval=600 value 600 represents 600 seconds i.e., 10 minutes.Īlternatively, add it to your ssh config file: Set it on your machine if you connect to multiple servers via SSH.Īnd several users complain about frequent SSH connection disconnect,
You can address this problem on either the client or the server. David's answer is OK, but a more comprehensive solution is explained below.
0 kommentar(er)
