Every session is expiring within 1 minute if it kept idle.


 
Thread Tools Search this Thread
Operating Systems Solaris Every session is expiring within 1 minute if it kept idle.
# 8  
Old 05-22-2008
Thanks for resolving my problem.

I had given 15 in putty for keepalive seconds.

Now its working fine.

Once again thanks.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Expiring password notifications

I have a Solaris 10 server that notified one of my users/database administrators of another users account expiring within X amount of days. It attempted to email the user@ server.com, which failed and was forwarded from the mailer-daemon@ server.com, to the DBA. She's not listed as an alias for... (2 Replies)
Discussion started by: Nvizn
2 Replies

2. Shell Programming and Scripting

Take minute per minute from a log awk

Hi, I've been trying to develop a script that performs the parsing of a log every 1 minute and then generating some statistics. I'm fairly new to programming and this is why I come to ask if I can lend a hand. this is my log: xxxx 16/04/2012 17:00:52 - xxxx714 - E234 - Time= 119 ms.... (8 Replies)
Discussion started by: jockx
8 Replies

3. UNIX for Dummies Questions & Answers

Non expiring password

Which files store the information about user with non expiring password in case of HP-UNIX like /etc/shadow in linux Two threads by Anu_1 merged (3 Replies)
Discussion started by: Anu_1
3 Replies

4. Solaris

Kill idle dt session

Hi, i need to kill the idle dt sessions through script, can anyone tell me how to do? RJS (2 Replies)
Discussion started by: rajasekg
2 Replies

5. UNIX for Dummies Questions & Answers

Every session is expiring within 1 minute if it kept idle.

Still it is not working. I had given 200 in putty but still it is expiring within 1 minute. (1 Reply)
Discussion started by: vamshikrishnab
1 Replies

6. Solaris

Extension of passwd expiring

Hi all, Anyway to reset the passwd expiring time without user having to reset it themselve? Beside altering the maximum number of days the password is valid in the shadow file, is there any other ways? Reason, user forgot passwd and the account passwd cannot be reset, same passwd is need for... (3 Replies)
Discussion started by: egls
3 Replies

7. Shell Programming and Scripting

FTP session expiring when transferring files... Need some solution

Hi All, I am running a ftp script which is running fine even with crontab. But the problem is that when I connect to ftp server and transfer files , i observe that ftp session expires after few minutes and the file transfer is not completed as there are alot of files to be transfered . ... (4 Replies)
Discussion started by: aarora_98
4 Replies

8. AIX

Knowing when is the user id expiring

HI, Do we have a command in AIX which will let us know when is the user id password getting expired!! Any advice will be of great help!! Thanks, Siddharth (0 Replies)
Discussion started by: siddhhuu
0 Replies

9. Cybersecurity

Killing Idle session

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
Login or Register to Ask a Question
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)