- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- auto disconnect
Operating System - HP-UX
1821052
Members
2337
Online
109631
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
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
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
тАО11-23-1999 08:39 PM
тАО11-23-1999 08:39 PM
auto disconnect
I am constantly running into the situation where users do not logoff of the HP
Server for periods (weeks) at a time.
Rather than killing the processes one by one, is there a 'nice' way to setup a
cron entry to do this every 6 hours or so. By nice, I mean that I do not run
the risk of crashing the database (progress) or crashing the machine.
Any insights would be great to have.
Thanks,
Nickd
Server for periods (weeks) at a time.
Rather than killing the processes one by one, is there a 'nice' way to setup a
cron entry to do this every 6 hours or so. By nice, I mean that I do not run
the risk of crashing the database (progress) or crashing the machine.
Any insights would be great to have.
Thanks,
Nickd
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-1999 10:27 PM
тАО11-23-1999 10:27 PM
Re: auto disconnect
Hi,
I guess you could write a script that would do such a thing but I really think
you should be carefull.
You could use the output of "who -u" to get the logon-date which you could
match with the current date. This command also gives the pid which you could
use to kill the connection. Please realize that users who have big jobs running
could loose a whole lot of work by killing them.
I guess you could write a script that would do such a thing but I really think
you should be carefull.
You could use the output of "who -u" to get the logon-date which you could
match with the current date. This command also gives the pid which you could
use to kill the connection. Please realize that users who have big jobs running
could loose a whole lot of work by killing them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-1999 11:10 PM
тАО11-23-1999 11:10 PM
Re: auto disconnect
If you use either the ksh or posix shell as the default user login shell, then
you can set the TMOUT parameter ot end the user's shells after a set period of
inactivity. This can be set in either individual user profiles or in
/etc/profile or both (default and customized values). A couple of notes:
1) The shells can be compiled with a maximum value (in seconds) for TMOUT. I
do not know whether this is the case in HP.
2) Inactivity is defined as seconds without a carriage return since the $PS1
prompt was last displayed.
2a) Because of (2), long jobs running in the background are vulnerable to
termination if you use TMOUT. Make sure that is reasonable in your environment
and notify your users where appropriate.
3) If you allow your users to maitain there own .profiles, they can easily
override the system default.
4) man ksh & man sh-posix for more details
you can set the TMOUT parameter ot end the user's shells after a set period of
inactivity. This can be set in either individual user profiles or in
/etc/profile or both (default and customized values). A couple of notes:
1) The shells can be compiled with a maximum value (in seconds) for TMOUT. I
do not know whether this is the case in HP.
2) Inactivity is defined as seconds without a carriage return since the $PS1
prompt was last displayed.
2a) Because of (2), long jobs running in the background are vulnerable to
termination if you use TMOUT. Make sure that is reasonable in your environment
and notify your users where appropriate.
3) If you allow your users to maitain there own .profiles, they can easily
override the system default.
4) man ksh & man sh-posix for more details
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP