- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Disconnect user session automatically
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
тАО06-21-2006 02:04 PM
тАО06-21-2006 02:04 PM
Thanks a lot.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 03:27 PM
тАО06-21-2006 03:27 PM
Re: Disconnect user session automatically
Hitman is possibly the best known of those.
There is even a OpenVMS FAQ entry for it:
http://vmsone.com/~ovmsfreeware/ovmsfwv6/disk2/vmsfaq/vmsfaq_007.html
Google for: +openvms +freeware +"idle process"
I personally don't like any of them, as I believe they cause excessive overhead, end user annoyance and only a false sense of safety.
Specifically, if I have a telnet/puTTY session on a 'locked' PC, then there is no way VMS based sofware can see whether this is safe or not. So they kill it, and then I have to transmit my password over the line again, create a new process, re-execute my environment setup, loose my recall buffers.
Thanks for nothing!
Still, I suppose you gotta do what you gotta do!
Cheers,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 03:29 PM
тАО06-21-2006 03:29 PM
Re: Disconnect user session automatically
How are the users connecting? Are they using Telnet, or DECserver connections?
Depending on the connection type, there are a number of ways to force them off.
Also, do you want to check if they are actually doing anything, or just dump them at a certain time?
Allan in Atlanta
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 03:39 PM
тАО06-21-2006 03:39 PM
Re: Disconnect user session automatically
Actually, we use the emulation software Reflection-X (thru REXEC) and Excursion (thru TELNET) to connect to Alpha system. If there has any checking before we kill the session, that would be definitely a benefit.
Thanks in advance.
Edmond
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 06:32 PM
тАО06-21-2006 06:32 PM
SolutionPS.I've slightly modified it to take out some site specific stuff. It's a bit more friendly than a just kill everyone routine. Doesn't do any checking to see if the user/pid is actually doing anything.
John.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 07:16 PM
тАО06-21-2006 07:16 PM
Re: Disconnect user session automatically
here we use the WATCHER package from H.Goatley.
It is very flexible. You find it here:
http://www.madgoat.com/watcher.html
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 08:09 PM
тАО06-21-2006 08:09 PM
Re: Disconnect user session automatically
It does depend on your environment.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-22-2006 11:22 AM
тАО06-22-2006 11:22 AM
Re: Disconnect user session automatically
They give a false sense of security and if not very carefully written, in extreme cases can cause some very nasty things to happen (for example, if you're running an IPK, never let your process count exceed BALSETCNT). They also encourage users to come up with mechanisms that defeat the IPK. Very easy to do, and generally wasteful of resources.
Rather than kill the process suspected of being idle, a better option would be to enable virtual terminals and disconnect the TELNET connection. That way the user can log back in to the session without losing any work. I'm not sure if any of the off-the-shelf solutions are capable of doing this.
That's all if you're attempting to figure out if a particular process idle from "outside" (even in theory, practically impossible). On the other hand, if you're writing an application with some kind of command loop, it's very easy to impose a timeout on command input and exit/logoff cleanly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-22-2006 11:44 AM
тАО06-22-2006 11:44 AM
Re: Disconnect user session automatically
I am not endorsing KBLOCK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-22-2006 04:43 PM
тАО06-22-2006 04:43 PM
Re: Disconnect user session automatically
>We use KBLOCK with a modified routine
>that starts with a $FORCEX followed by
>$DELPRC. Further the application has an
>exit handler which responds to $forcex.
>Works most of the time.
If the application has an exit handler especially written to handle an IPK, why not just implement the idle timeout in the application itself and avoid all the potential problems? Much easier to issue a command READ with a timeout and take the timeout condition to be equivalent to an EXIT command. Very simple, very effective and much safer than shooting processes.