05-21-2008
Every session is expiring within 1 minute if it kept idle.
Hi,
I am accessing a solaris server via client machine.
My problem is that every session is expiring within 1 minute if it kept idle. I am facing problem as i have to enter the credentials around 30 to 40 times per day.
I tried to set the TMOUT variable but it does n't work.
Please help me in resolving this.
9 More Discussions You Might Find Interesting
1. Cybersecurity
does any one know how to kill an idle session?
I want to kill any idle sessions after 30 min... Local or remote....
i want to do this without a script or TCP wrappers...i want to know if there is a file that i can configure.....
ThAnks:rolleyes: (4 Replies)
Discussion started by: securhack
4 Replies
2. AIX
HI,
Do we have a command in AIX which will let us know when is the user id password getting expired!!
Any advice will be of great help!!
Thanks,
Siddharth (0 Replies)
Discussion started by: siddhhuu
0 Replies
3. Shell Programming and Scripting
Hi All,
I am running a ftp script which is running fine even with crontab. But the problem is that when I connect to ftp server and transfer files , i observe that ftp session expires after few minutes and the file transfer is not completed as there are alot of files to be transfered .
... (4 Replies)
Discussion started by: aarora_98
4 Replies
4. Solaris
Hi all,
Anyway to reset the passwd expiring time without user having to reset it themselve? Beside altering the maximum number of days the password is valid in the shadow file, is there any other ways?
Reason, user forgot passwd and the account passwd cannot be reset, same passwd is need for... (3 Replies)
Discussion started by: egls
3 Replies
5. UNIX for Dummies Questions & Answers
Still it is not working.
I had given 200 in putty but still it is expiring within 1 minute. (1 Reply)
Discussion started by: vamshikrishnab
1 Replies
6. Solaris
Hi,
i need to kill the idle dt sessions through script, can anyone tell me how to do?
RJS (2 Replies)
Discussion started by: rajasekg
2 Replies
7. UNIX for Dummies Questions & Answers
Which files store the information about user with non expiring password in case of HP-UNIX like /etc/shadow in linux
Two threads by Anu_1 merged (3 Replies)
Discussion started by: Anu_1
3 Replies
8. Shell Programming and Scripting
Hi, I've been trying to develop a script that performs the parsing of a log every 1 minute and then generating some statistics. I'm fairly new to programming and this is why I come to ask if I can lend a hand.
this is my log:
xxxx 16/04/2012 17:00:52 - xxxx714 - E234 - Time= 119 ms.... (8 Replies)
Discussion started by: jockx
8 Replies
9. Solaris
I have a Solaris 10 server that notified one of my users/database administrators of another users account expiring within X amount of days. It attempted to email the user@ server.com, which failed and was forwarded from the mailer-daemon@ server.com, to the DBA. She's not listed as an alias for... (2 Replies)
Discussion started by: Nvizn
2 Replies
LEARN ABOUT DEBIAN
mosh-client
MOSH(1) General Commands Manual MOSH(1)
NAME
mosh-client - client-side helper for mosh
SYNOPSIS
MOSH_KEY=KEY mosh-client IP PORT
mosh-client -c
DESCRIPTION
mosh-client is a helper program for the mosh(1) remote terminal application.
mosh itself is a setup script that establishes an SSH connection, runs the server-side helper mosh-server, and collects the server's port
number and session key.
mosh then executes mosh-client with the server's IP address, port, and session key. mosh-client runs for the lifetime of the connection.
The 22-byte base64 session key given by mosh-server is supplied in the MOSH_KEY environment variable. This represents a 128-bit AES key
that protects the integrity and confidentiality of the session.
For constructing new setup wrappers for remote execution facilities other than SSH, it may be necessary to invoke mosh-client directly.
With the -c option, mosh-client instead prints the number of colors of the terminal given by the TERM environment variable.
SEE ALSO
mosh(1), mosh-server(1).
Project home page: http://mosh.mit.edu
AUTHOR
mosh was written by Keith Winstein <mosh-devel@mit.edu>.
BUGS
Please report bugs to mosh-devel@mit.edu. Users may also subscribe to the mosh-users@mit.edu mailing list, at
http://mailman.mit.edu/mailman/listinfo/mosh-users
February 2012 MOSH(1)