- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Inactivity Logout
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2010 06:48 AM
тАО08-31-2010 06:48 AM
Fred
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2010 08:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2010 10:46 AM
тАО08-31-2010 10:46 AM
Re: Inactivity Logout
TMOUT will work for shell sessions that are idle.
Once an app is fired up, the app needs to take care of this function.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2010 12:24 AM
тАО09-01-2010 12:24 AM
Re: Inactivity Logout
# echo $TMOUT
0
# export TMOUT=5
# echo $TMOUT
5
#
Shell will time out in 60 seconds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2010 01:04 AM
тАО09-01-2010 01:04 AM
Re: Inactivity Logout
TMOUT:
You can configure the TMOUT variable to automatically lock inactive terminals.
If you use other systems often and if you copy the .profile file from one system to
another, then adding the TMOUT variable to the .profile is more convenient. If you
typically stay on one system, then either method of locking the terminal can be used.
To configure the TMOUT variable, edit the .profile file as shown in the following:
# vi ~/.profile
export TMOUT=600 # (lock after 600 seconds of inactivity)
You can change the 600 to another desired value.
CDE LOCK:
You can configure the CDE lock manager to lock your screen after a certain amount of
inactive time. To configure the CDE lock manager to lock the screen after 10 minutes
of inactive time, enter the following commands:
# cp /usr/dt/config/C/sys.resources /etc/dt/config/C/sys.resources
# vi /etc/dt/config/C/sys.resources
dtsession*lockTimeout: 10
You can also use the Style Manager task panel to adjust the CDE lock manager. To do
this, click on the screen icon.
rgs,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2010 01:14 AM
тАО09-01-2010 01:14 AM
Re: Inactivity Logout
If you send a "kill -HUP" to the user's dtsession process, that should kill the entire CDE session in a controlled fashion.
I don't have a workstation system available right now so I cannot check... but if the screen saver/locker causes a recognizable process to appear when it's active, it might be possible to use it as "inactivity indicator", so a relatively simple script or program should be able to detect the sessions that have been inactive for too long.
Pseudo-code:
if (there is a dtsession process running) {
identify the user running the session
if (the session has a screensaver running) {
find the start time of the screensaver process
screensaver.runtime = current_time - screensaver.starttime
if (screensaver.runtime > inactivity limit) {
kill -HUP
}
}
}
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2010 10:22 PM
тАО09-01-2010 10:22 PM
Re: Inactivity Logout
>Shell will time out in 60 seconds.
That's 5 seconds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2010 10:39 PM
тАО09-01-2010 10:39 PM
Re: Inactivity Logout
>>Shell will time out in 60 seconds.
>That's 5 seconds.
Yes , it is weird, is there any other parameter to set minimum timeout like 60 seconds ??
$ uname -a
HP-UX igui01 B.11.11 U 9000/800 1889900691 unlimited-user license
$ export TMOUT=1
$
shell time out in 60 seconds
$ export TMOUT=61
$ echo $TMOUT
61
$
shell time out in 60 seconds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2010 11:26 PM
тАО09-01-2010 11:26 PM
Re: Inactivity Logout
Hmm, you're saying it doesn't work as documented?
I suppose we could use tusc to see how it works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-02-2010 12:08 AM
тАО09-02-2010 12:08 AM
Re: Inactivity Logout
export TMOUT=120
after an elapse of about two minute I get the...
Shell will time out in 60 seconds.
...prompt. A minute later the session disconnects.
If I interact before the 60 seconds expire, then I get another two minutes before being prompted again.
So, from my observation it seems to work, more or less, as expected.
The 60 second warning does not appear if I'm using bash but the session terminates all the same!