07-23-2001
thanx but...this prameter only works for ROOT and not regular users. i have trired putting this prameter in .profile of the user, in the /etc/default/login, in the /etc/default/telnetd for telnet sessions and none of them have been successful...
Last edited by Holistic; 07-24-2001 at 05:51 PM..
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm looking for some help, please!
I'm trying to kill any idle user processes over 40 Minutes.
I have tried putting TMOUT=2400
within the users .profile
However this does not seem to be working.
We run aix 4.3.3
with ORACLE 7.3
The above works o.k. when the user is only within the... (3 Replies)
Discussion started by: annette
3 Replies
2. Shell Programming and Scripting
I need a script that will look for idle users and kill there proc. (7 Replies)
Discussion started by: jdel80
7 Replies
3. Shell Programming and Scripting
I wrote a script to kill users idle more than 1/2 hour, ignoring those in an exception list. Here is the script as it is now:
#! /usr/bin/awk -f
BEGIN {
system("who -u | sort +5 > /tmp/loginfile");
system("echo User Sessions Killed > /tmp/killedlogins");
... (2 Replies)
Discussion started by: PapaBear
2 Replies
4. 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
5. Solaris
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... (7 Replies)
Discussion started by: vamshikrishnab
7 Replies
6. Shell Programming and Scripting
Hello,
I am new to unix scripts and have been experimenting with do-while structure. I have run into a problem.
my script is,
---
while true
do
./redir --lport=55083 --caddr=14.121.119.21 --cport=55083 2>&1 >> /tmp/out.txt
echo "Restarting `date`"
done
---
As you can see, i didnt handle... (3 Replies)
Discussion started by: script_newbie
3 Replies
7. Shell Programming and Scripting
Hi All,I have a problem with my kill idle script.my script is supposed to kill the user sessions which are idle for more than 2 hours.But is is killing the sessions which are idle for less than 2 hrs also.I dont know the exact time after which the script is killing,but it is less than 2 hours i am... (3 Replies)
Discussion started by: prabhu_kumar
3 Replies
8. 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
9. HP-UX
Hi,
I have this Unix script that kills a user session. When I run it, my screen goes blank. How do I prevent the blank screen?
Ex: I open 2 Unix sessions. The main PID for my 1st session is 1234. In the second session I issue a "kill -HUP 1234". The first session gets killed but the second... (5 Replies)
Discussion started by: rm-r
5 Replies
LEARN ABOUT ULTRIX
telnetd
telnetd(8c) telnetd(8c)
Name
telnetd - DARPA TELNET protocol server
Syntax
/etc/telnetd
Description
The server supports the DARPA standard TELNET virtual terminal protocol. The TELNET server is invoked when receives a connection request
on the port indicated in the TELNET service description.
The server operates by allocating a pseudo-terminal device for a client, then creating a login process which has the slave side of the
pseudo-terminal as stdin, stdout, and stderr. The server manipulates the master side of the pseudo terminal, implementing the TELNET pro-
tocol and passing characters between the client and login process.
When a TELNET session is started up, sends a TELNET option to the client side indicating a willingness to do remote echo of characters, to
suppress go ahead, and to receive terminal type information from the remote client. If the remote client is willing, the remote terminal
type is propagated in the environment of the created login process. The pseudo terminal allocated to the client is configured to operate
in cooked mode and with XTABS and CRMOD enabled.
Aside from this initial setup, the only mode changes will carry out are those required for echoing characters at the client side of the
connection.
The server supports binary mode, suppress go ahead, echo, and timing mark. It also allows a remote client to do binary, terminal type, and
suppress go ahead.
Restrictions
Some TELNET commands are only partially implemented.
The TELNET protocol allows the exchange of the number of lines and columns on the user's terminal, but does not make use of them.
The terminal type name received from the remote client is converted to lower case.
The server never sends TELNET go ahead commands.
See Also
telnet(1c), pty(4), tty(4), services(5), inetd(8c)
telnetd(8c)