12-14-2005
script for killing idle users
I need a script that will look for idle users and kill there proc.
10 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. 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
3. HP-UX
My max user parm is set to 1050. I'm currently at 1038 this is causing major slow downs on the server. I looking for a way log off "idle" user logins with out having to do it individually. :confused: (5 Replies)
Discussion started by: rfmurphy_6
5 Replies
4. AIX
How to set a timer for log out users that have been idle for a long time? It is a AIX 5L (0 Replies)
Discussion started by: wtofu
0 Replies
5. Shell Programming and Scripting
I am trying to write a script that will list the idle users on my system which is running HPUX 11.11. The script is currently written as :
who -u > /home/rfm/scripts/user.txt
echo " There are currently... "
wc -l /home/rfm/scripts/user.txt
echo " User logins on System : `uname -n` ... (3 Replies)
Discussion started by: rfmurphy_6
3 Replies
6. Shell Programming and Scripting
Please help, im modifing an idle script to capture (not kill) users who havee been idle over a time. now i've got to work with the exection of users whos idle time gove over 24 hrs and becomes "old". please advice on how to correct...
#Clear old report, generate new data and new report
echo "\n... (1 Reply)
Discussion started by: pbonilla
1 Replies
7. UNIX for Advanced & Expert Users
Im "supporting" at least 2500 HP-UX workstations with CAD-related software with the B.11.11 build. I cant say anymore than that because of my companys sligtly paranoid security policy .
The last few days a new problem has arised from nowhere.
The problem is that users gets logged off when the... (5 Replies)
Discussion started by: Laoinjo
5 Replies
8. 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
9. HP-UX
Hi,
In my network we uses the NetTerm program to connect us to HP-UX 10.x server from windows workstations, but in some cases the user doesn't logout and close it by window's x button. The problem is that in HP-UX the user and all his tasks remain active and when he enter again HP-UX creates a... (12 Replies)
Discussion started by: efrenba
12 Replies
10. 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
LEARN ABOUT OSX
tcl_cancelidlecall
Tcl_DoWhenIdle(3) Tcl Library Procedures Tcl_DoWhenIdle(3)
__________________________________________________________________________________________________________________________________________________
NAME
Tcl_DoWhenIdle, Tcl_CancelIdleCall - invoke a procedure when there are no pending events
SYNOPSIS
#include <tcl.h>
Tcl_DoWhenIdle(proc, clientData)
Tcl_CancelIdleCall(proc, clientData)
ARGUMENTS
Tcl_IdleProc *proc (in) Procedure to invoke.
ClientData clientData (in) Arbitrary one-word value to pass to proc.
_________________________________________________________________
DESCRIPTION
Tcl_DoWhenIdle arranges for proc to be invoked when the application becomes idle. The application is considered to be idle when
Tcl_DoOneEvent has been called, could not find any events to handle, and is about to go to sleep waiting for an event to occur. At this
point all pending Tcl_DoWhenIdle handlers are invoked. For each call to Tcl_DoWhenIdle there will be a single call to proc; after proc is
invoked the handler is automatically removed. Tcl_DoWhenIdle is only usable in programs that use Tcl_DoOneEvent to dispatch events.
Proc should have arguments and result that match the type Tcl_IdleProc:
typedef void Tcl_IdleProc(ClientData clientData);
The clientData parameter to proc is a copy of the clientData argument given to Tcl_DoWhenIdle. Typically, clientData points to a data
structure containing application-specific information about what proc should do.
Tcl_CancelIdleCall may be used to cancel one or more previous calls to Tcl_DoWhenIdle: if there is a Tcl_DoWhenIdle handler registered for
proc and clientData, then it is removed without invoking it. If there is more than one handler on the idle list that refers to proc and
clientData, all of the handlers are removed. If no existing handlers match proc and clientData then nothing happens.
Tcl_DoWhenIdle is most useful in situations where (a) a piece of work will have to be done but (b) it is possible that something will hap-
pen in the near future that will change what has to be done or require something different to be done. Tcl_DoWhenIdle allows the actual
work to be deferred until all pending events have been processed. At this point the exact work to be done will presumably be known and it
can be done exactly once.
For example, Tcl_DoWhenIdle might be used by an editor to defer display updates until all pending commands have been processed. Without
this feature, redundant redisplays might occur in some situations, such as the processing of a command file.
BUGS
At present it is not safe for an idle callback to reschedule itself continuously. This will interact badly with certain features of Tk
that attempt to wait for all idle callbacks to complete. If you would like for an idle callback to reschedule itself continuously, it is
better to use a timer handler with a zero timeout period.
KEYWORDS
callback, defer, idle callback
Tcl 7.5 Tcl_DoWhenIdle(3)