ClientAliveCountMax
Sets the number of client alive messages (see Clien-
tAliveInterval, below) that can be sent without sshd
receiving any messages back from the client. If this
threshold is reached while client alive messages are
being sent, sshd disconnects the client, terminating the
session. It is important to note that the use of client
alive messages is very different from KeepAlive (see
below). The client alive messages are sent through the
encrypted channel and therefore are not spoofable. The
TCP keepalive option enabled by KeepAlive is spoofable.
The client alive mechanism is valuable when a client or
server depend on knowing when a connection has become
inactive.
The default value is 3. If ClientAliveInterval (below)
is set to 15, and ClientAliveCountMax is left at the
default, unresponsive ssh clients are disconnected after
approximately 45 seconds.
We are facing difficulties in ftp'ing large files.For large file transfer using FTP, the control session gets timed out where as the the data session is active and transfers the file completely. Is there a way to make the control session active as long as data session?
How to find the control... (1 Reply)
I am executing test.sh script. But this script takes lot of time and in the meantime the shell timeouts without completing the script.
Is there any command which will continue processing the script.
Thanks (3 Replies)
We recently moved servers to a new data center, and now we're experiencing user sessions timing out after non-activity. We didnt experience this before, or know of any timeout settings that may have been changed.
Any things I can check out on the server? (3 Replies)
Hi,
I had add the following line into .profile and .bash_profile for the timeout session to avoid putty close automatically :
timeout=10800
However, i still keep encounter session time out every after 60 seconds.
Can anyone please help advice.
Many Thanks! (2 Replies)
Hi
I'm writing a script which based on a condition, restarts a set of servers. The problem I'm facing is, say if one of the server is down, my script stops there and fails to proceed. How can I ensure to set a timeout value on that script, so when the server is not reachable, the script should... (2 Replies)
Friends,
Could anyone let me know - how to set the timeout value for ssh session to HMC? My HMC version is -- V7R7.4.0. I'm sure the version doesn't have anything to do with it.
Thanks,
-- Souvik (2 Replies)
Hello friends,
I work on Linux servers via SSH (putty) and run "screen" to preserve my sessions so I can attach/detach them at anytime I wish without losing the connectivity/process disruption which is working perfectly fine.
As my team members also have root access to those servers, it is... (7 Replies)
Discussion started by: prvnrk
7 Replies
LEARN ABOUT POSIX
chsh
CHSH(1) User Commands CHSH(1)NAME
chsh - change login shell
SYNOPSIS
chsh [options] [LOGIN]
DESCRIPTION
The chsh command changes the user login shell. This determines the name of the user's initial login command. A normal user may only change
the login shell for her own account; the superuser may change the login shell for any account.
OPTIONS
The options which apply to the chsh command are:
-h, --help
Display help message and exit.
-R, --root CHROOT_DIR
Apply changes in the CHROOT_DIR directory and use the configuration files from the CHROOT_DIR directory.
-s, --shell SHELL
The name of the user's new login shell. Setting this field to blank causes the system to select the default login shell.
If the -s option is not selected, chsh operates in an interactive fashion, prompting the user with the current login shell. Enter the new
value to change the shell, or leave the line blank to use the current one. The current shell is displayed between a pair of [ ] marks.
NOTE
The only restriction placed on the login shell is that the command name must be listed in /etc/shells, unless the invoker is the superuser,
and then any value may be added. An account with a restricted login shell may not change her login shell. For this reason, placing /bin/rsh
in /etc/shells is discouraged since accidentally changing to a restricted shell would prevent the user from ever changing her login shell
back to its original value.
FILES
/etc/passwd
User account information.
/etc/shells
List of valid login shells.
/etc/login.defs
Shadow password suite configuration.
SEE ALSO chfn(1), login.defs(5), passwd(5).
shadow-utils 4.5 01/25/2018 CHSH(1)