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 OSX

glutidlefunc

glutIdleFunc(3GLUT)						       GLUT						       glutIdleFunc(3GLUT)

NAME

       glutIdleFunc - sets the global idle callback.

SYNTAX

       #include <GLUT/glut.h>

       void glutIdleFunc(void (*func)(void));

ARGUMENTS

       func	 The new idle callback function.

DESCRIPTION

       glutIdleFunc  sets  the	global	idle callback to be func so a GLUT program can perform background processing tasks or continuous animation
       when window system events are not being received. If enabled, the idle callback is continuously called when events are not being  received.
       The  callback  routine  has no parameters. The current window and current menu will not be changed before the idle callback.  Programs with
       multiple windows and/or menus should explicitly set the current window and/or current menu and not rely on its current setting.

       The amount of computation and rendering done in an idle callback should be minimized to avoid affecting the program's interactive response.
       In general, not more than a single frame of rendering should be done in an idle callback.

       Passing NULL to glutIdleFunc disables the generation of the idle callback.

EXAMPLE

       A typical idle callback to animate a window might look like:

	 void
	 idle(void)
	 {
	   time += 0.05;
	   glutSetWindow(window);
	   glutPostRedisplay();
	 }

       Notice  how  the  idle callback does not do any actual drawing; it only advances the time scene state global variable.  That is left to the
       window's display callback which will be triggered by the call to glutPostRedisplay.

       If you use the idle callback for animation, you should be sure to stop rendering when the window is not visible.  This is easy  to  set	up
       with a visibility callback.  For example:

	 void
	 visible(int vis)
	 {
	   if (vis == GLUT_VISIBLE)
	     glutIdleFunc(idle);
	   else
	     glutIdleFunc(NULL);
	 }

       If  you	do use the idle callback for animation, one thing you should not do is setup the idle callback before calling glutMainLoop.  It is
       much better to use the visibility callback to install idle callback when the window first becomes visible on the screen.

SEE ALSO

       glutTimerFunc, glutVisibilityFunc

AUTHOR

       Mark J. Kilgard (mjk@nvidia.com)

GLUT
									3.7						       glutIdleFunc(3GLUT)

AIX