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 sure.I faced this problem personelly with my session also.i opened a new session of my application and after half an hour or so it got killed by the shell idle script.Here I am giving my kill idle script.Please if any one can make it out where the problem is that could be great.
Last edited by pludi; 03-04-2010 at 08:00 AM..
Reason: code tags, please...
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)
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)
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)
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)
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)
Dear Friends ,
I am using DB2 database in AIX 5.3 server . In my server some IDLE process are generated after several times which I need to kill it manually each and every time .
The process I query like following :
root@bagpuss $ ps auxw|sort -r +3|head -10
USER PID %CPU %MEM ... (3 Replies)
Hi,
I need a script that can automatically kill all processes named "webrepn" and "webrebw" if idle for more than 30 minutes.
Then I will have a Cron Job to run the script every night or 2-3 times a day depends on how this script helps.
Right now, I run "ps -ef | grep webrebn" and "kill -9... (7 Replies)
I originally had a script written in pure shell that I used to parse logs in real time and create a pipe delimited file that only contained errors. It worked but it was using a lot of memory (still not clear on why). I originally got around this by writing a wrapper for the script that ran on cron... (1 Reply)
Discussion started by: DeCoTwc
1 Replies
LEARN ABOUT MOJAVE
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)