|
|
Sponsored Content
Special Forums
Cybersecurity
Killing Idle session
Post 4268 by Holistic on Monday 23rd of July 2001 08:46:21 AM
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 HPUX
nstrtel
nstrtel(5) File Formats Manual nstrtel(5) NAME
nstrtel - specifies the number of telnet device files the kernel can support for incoming telnet sessions VALUES
Failsafe Default Allowed values (Subject to available physical memory.) It is best to use the default value, and there should not be any need to lower it. However, if the simultaneous telnet connection load is very high, then the value of could be increased. Recommended values (Default value.) DESCRIPTION
The telnet daemon uses two STREAMS-based pseudo-terminal drivers and The kernel parameter, can be used to tune the number of pseudo-termi- nals. specifies the number of kernel data structures that are created at system boot time that are required to support the device files used by incoming telnet sessions on a server. If the command or SAM is used to create more telnet device files, the value of must be increased accordingly or the device files cannot be used because there are no kernel data structures available for communicating with the system. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect at the next reboot. When Should the Value of This Tunable Be Raised? When there is an increase in the load of telnet connections and there are no device files available to open telnet connections, then this kernel parameter should be increased. When the error is encountered, then the device files have been exhausted and should be raised. Once the value of is raised, should be run to create new device files. (If SAM is used to raise the value of is run automatically.) What Are the Side Effects of Raising the Value of This Tunable? More resources would be consumed. Extra kernel data structures, and extra device files may clog the system. When Should the Value of This Tunable Be Lowered? It is not advisable to lower the tunable value from the default value. Consult HP Support before lowering this tunable from the default value. What Are the Side Effects of Lowering the Value of This Tunable? Though not recommended, there would not be any side effects. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
insf(1M), telnetd(1M), telm(7), tels(7). Tunable Kernel Parameters nstrtel(5)