Log off idle users

10 More Discussions You Might Find Interesting

1. AIX

Telnet sessions stay as idle users

Hi The telnet sessions stay as idle users. It is not getting kicked out. Please advise what could be the issue. only when we reboot the server these telnet sessions goes. Below is the current output from the server. we rebooted the server three days ago: pmut6:/> uptime 04:21PM...

2. Solaris

Logging out idle users after a certain timeframe

We recently underwent a security audit and have a new requirement to not allow users to stay logged on overnight. In order to place this policy into effect i need a way to check for idle users and log them off. Is there any good way to enforce this policy in Solaris 10 and make it work in such a...

3. HP-UX

kill idle users

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...

4. Shell Programming and Scripting

Killing idle users TIA

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"); ...

5. UNIX for Advanced & Expert Users

HP-UX users get logged off while idle.

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...

6. Shell Programming and Scripting

i need a scipt to email users with idle processes!?

hello, i am VERY new to this whole script world. I need to come up with a script that will email a user if they have an idle process past 500 minutes...any suggestions??? Thanks so much.

7. Shell Programming and Scripting

Idle users over 1 day

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...

8. Shell Programming and Scripting

script for killing idle users

I need a script that will look for idle users and kill there proc.

9. Shell Programming and Scripting

finding idle users

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` ...

10. HP-UX

Is there a script available to kill Idle users

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:

LEARN ABOUT MOJAVE

update

update(n)						       Tcl Built-In Commands							 update(n)

__________________________________________________________________________________________________________________________________________________

NAME

       update - Process pending events and idle callbacks

SYNOPSIS

       update ?idletasks?
_________________________________________________________________

DESCRIPTION

       This  command  is used to bring the application "up to date" by entering the event loop repeatedly until all pending events (including idle
       callbacks) have been processed.

       If the idletasks keyword is specified as an argument to the command, then no new events or errors are processed;  only idle  callbacks  are
       invoked.   This causes operations that are normally deferred, such as display updates and window layout calculations, to be performed imme-
       diately.

       The update idletasks command is useful in scripts where changes have been made to the application's state and you  want	those  changes	to
       appear  on  the display immediately, rather than waiting for the script to complete.  Most display updates are performed as idle callbacks,
       so update idletasks will cause them to run.  However, there are some kinds of updates that only happen in response to events, such as those
       triggered by window size changes; these updates will not occur in update idletasks.

       The update command with no options is useful in scripts where you are performing a long-running computation but you still want the applica-
       tion to respond to events such as user interactions;  if you occasionally call update then user input will be  processed  during  the  next
       call to update.

EXAMPLE

       Run computations for about a second and then finish:
	      set x 1000
	      set done 0
	      after 1000 set done 1
	      while {!$done} {
		  # A very silly example!
		  set x [expr {log($x) ** 2.8}]

		  # Test to see if our time-limit has been hit.  This would
		  # also give a chance for serving network sockets and, if
		  # the Tk package is loaded, updating a user interface.
		  update
	      }

SEE ALSO

       after(n), interp(n)

KEYWORDS

       event, flush, handler, idle, update

Tcl									7.5								 update(n)

AIX