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 DEBIAN

anyevent::aggressiveidle

AnyEvent::AggressiveIdle(3pm)				User Contributed Perl Documentation			     AnyEvent::AggressiveIdle(3pm)

NAME

       AnyEvent::AggressiveIdle - Aggressive idle processes for AnyEvent.

SYNOPSIS

	   use AnyEvent::AggressiveIdle qw(aggressive_idle};

	   aggressive_idle {
	       ... do something important
	   };

	   my $idle;
	   $idle = aggressive_idle {
	       ... do something important

	       if (FINISH) {
		   undef $idle;    # do not call the sub anymore
	       }
	   };

DESCRIPTION

       Sometimes You need to do something that takes much time but can be split into elementary phases. If You use AE::idle and Your program is a
       highload project, idle process can be delayed for much time (second, hour, day, etc). aggressive_idle will be called for each AnyEvent loop
       cycle. So You can be sure that Your idle process will continue.

EXPORTS

   aggressive_idle
       Register Your function as aggressive idle watcher. If it is called in VOID context, the watcher wont be deinstalled. Be carrefully.

       In NON_VOID context the function returns a guard.  Hold the guard until You want to cancel idle process.

   stop_aggressive_idle
       You can use the function to stop idle process. The function receives idle process PID that can be received in idle callback (the first
       argument).

       Example:

	   use AnyEvent::AggressiveIdle ':all'; # or:
	   use AnyEvent::AggressiveIdle qw(aggressive_idle stop_aggressive_idle);

	   aggressive_idle {
	       my ($pid) = @_;
	       ....

	       stop_aggressive_idle $pid;
	   }

       The function will throw an exception if invalid PID is received.

Continuous process.
       Sometimes You need to to something continuous inside idle callback. If You want to stop idle calls until You have done Your work, You can
       hold guard inside Your process:

	   aggressive_idle {
	       my ($pid, $guard) = @_;
	       my $timer;
	       $timer = AE::timer 0.5, 0 => sub {
		   undef $timer;
		   undef $guard;   # POINT 1
	       }
	   }

       Until 'POINT 1' aggressive_idle won't call its callback.  Feel free to stop_aggressive_idle before free the guard.

AUTHOR

       Dmitry E. Oboukhov, <unera@debian.org>

COPYRIGHT AND LICENSE

       Copyright (C) 2011 by Dmitry E. Oboukhov

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.10.1 or,
       at your option, any later version of Perl 5 you may have available.

VCS

       The project is placed on my GIT repo: <http://git.uvw.ru/?p=anyevent-aggressiveidle;a=summary>

perl v5.10.1							    2011-03-01					     AnyEvent::AggressiveIdle(3pm)

AIX