HP3000-L Archives

November 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Rutherford <[log in to unmask]>
Reply To:
Date:
Tue, 17 Nov 1998 15:15:21 -0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
The HPTIMEOUT variable is good so long as your session remains at the CI :
prompt. However, if your session is inside another process (Application,
qedit, query etc.) it has no effect and therefore its usefulness is limited.

Many thanks

David
(ex 4321)


        -----Original Message-----
        From:   Rick Clark [SMTP:[log in to unmask]]
        Sent:   17 November 1998 15:04
        To:     [log in to unmask]
        Subject:        Re: Monitor user's session activity

        * Please Note : This message was received from the Internet *
        _____________________________________________________________

        Try setting the variable HPTIMEOUT.

        :SETVAR HPTIMEOUT minutes

        ASNMNTS WWA:help hptimeout
        HPTIMEOUT   A variable used by the CI that lets a user set timed CI
                    reads on $STDIN. A positive value indicates the number
                    of minutes the CI waits for input.  If a timed CI read
                    expires, the session is logged off.  The initial value
                    is zero, which means no timed reads.  Type= W I PL



        [log in to unmask] wrote:
        >
        > System: HP3000
        > Server OS: MPE version 5
        > Client: Terminally Emulation program running on Win95
        >
        > Is there a way, such as running a script on the server,  to
monitor a user
        > session's activity ? Specially, we need to know if a user's
session has been
        > idle for a period of time and automatically kill that session.
        >
        > Any input will be greatly appreciate. If possible, please reply
with a copy:
        > mailto:[log in to unmask]
        >
        > Edmund

__________________________________________________________________

                Confidentiality Notice

This message may contain privileged and confidential information. If you think, for any reason, that this message may have been addressed to you in error, you must not disseminate, copy or take any action in reliance on it, and we would ask you to notify us immediately by return email to "[log in to unmask]".

ATOM RSS1 RSS2