- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- User idle time
Operating System - HP-UX
1753521
Members
6392
Online
108795
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО06-27-2000 10:34 AM
тАО06-27-2000 10:34 AM
How can I kick out users that are over an hour idle. A lot of my users don't log out at all. I know I can kick them out individually but wanted to know if there is some kind of setting out there that I am unaware of.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2000 11:01 AM
тАО06-27-2000 11:01 AM
Solution
I don't know of any automated command to do this, but here are some thoughts... There is an inherent danger with logging people out of a machine. Who knows what type of processing they are/have been performing. For example, they could be in some data entry screen within a RDBMS where the execution point there sitting on may not have written to all the required files. One hour idle time may seem long but I think it's a bit short when you consider the potential ramifications. A better method may be to log off inactive user processes when you perform your daily backups. The preferred method would be to use kill -1 (SIGHUP). My strong suggestion would be to discuss the issue with your DBA's and application developers before you set anything in stone. It's a good chance that they are the worst culprits to which the best solution is to relegate them to a separate test machine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2000 11:20 AM
тАО06-27-2000 11:20 AM
Re: User idle time
Hello,
For telnet sessoins you can try setting "TMOUT" shell variable in .profile to some number of seconds. Idle sessions will get dropped after specified period. Works for sure with ksh.
Regards,
TT
For telnet sessoins you can try setting "TMOUT" shell variable in .profile to some number of seconds. Idle sessions will get dropped after specified period. Works for sure with ksh.
Regards,
TT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2000 12:12 PM
тАО06-27-2000 12:12 PM
Re: User idle time
Both good answers. If you simply must find users to boot on the basis of idle time, then you can parse the value out of w (or uptime). This works for any users that connect through a standard login shell, but it will not find users that hit the box through an applications socket which does not spawn a shell session.
One note: make sure to select processes to kill based upon tty, not userid, since a user may have multiple logins open.
One note: make sure to select processes to kill based upon tty, not userid, since a user may have multiple logins open.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP