Conference vaxaxp::vmsnotes

   The Assets ZAP product is being discussed over in the European Assets
   notes conference -- from what I can tell, the entire Assets program
   is currently undergoing a reorganization.  See CLARID::EOASSETS.

   ZAP was retired a while back.  Also see the ZAP notes conference at
   SHARE::ZAP.  (If you're not sure about the location or the name of a
   notes conference, "search humane::sys$public:easynotes.lis zap"...)

   There are third-party idle-process killers available from a variety
   of sources, and freeware available from DECUS and other sources.

Roberto,
   If you cannot get an answer regarding ZAP please keep in mind
  that some of our partners sell products that will solve this
  problem on OpenVMS for your customer.
   Two products that I can think of off the top of my head are
  Axent's KBLOCK and Braintree's VIGIL. I think OpenVISION has
  a product that does something similar as well. 

                                          - Leo Demers
                                          OpenVMS & SEVMS 
                                          Security Product Manager
                                          Tel: (603)881-2245
                                          DTN:381-2245
  

re .0
    
>He would like to kill user processes logged but inactive during the
>night, and for this requirement doesn't help setting hours, days or
>minutes in specific accounts (this blocks only possible new logins).
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    
    False.
    
    If you are logged in and the hour rolls over and you would not now be
    allowed to log in, you will be killed by VMS with the following message.
    
%SYSTEM-F-FORCEDEXIT, forced exit of image or process by job controller
    
    However this makes no distinction as to whether the process was idle
    and so may not meet the customer's stated requirements.
    
    As always when the topic of IPKs comes up, the question arises as to
    why they feel they need to do this.

Hi to all,
          many thanks for your quick suggestions. 

Best regards,
             Roberto.

>         <<< Note 313.3 by AUSS::GARSON "DECcharity Program Office" >>>
>
>    As always when the topic of IPKs comes up, the question arises as to
>    why they feel they need to do this.

I'm only guessing, but one reason could be due to license restrictions.  Unlike
our internal systems, many customers are not licensed for unlimited use. 
Therefore, inactive/idle logins can prevent people with real work from logging
in.

Perhaps if we had to work under the same conditions, there would be hooks in
the operating system to make things easier (and less kludgy) for tools like
ZAP.

Eric

    ahem...
    having worked on KBlock a bit, I'll mention that the XAutolock program
    might also be considered for idle workstations. KBlock is otherwise
    rather unaware of X connections. One can, with recent Digital X
    servers, do rather better since they implement the xidle extension
    but with older Digital X code, XAutolock needs to get in the input
    chain. It does run on VMS however, and is reliable.
    
    For terminals, I like WATCHER (free, from DECUS, sigtapes, or net)
    and have used it. However, the ability to lock a terminal via a
    terminal port/class intercept and block terminal traffic with no
    other effect is unique to KBlock. The others can suspend processes,
    stop them, forcex, or in a few cases detach them. Last I heard
    of, KBlock was only on Vax, but may have been ported by now.
    (One obstacle when I worked with it was that a good chunk of the
    code was in Vax BASIC. I think they were translating it all to C
    though.)
    glenn everhart
    

    Here's some pointers to the products I mentioend earlier.
      Kblock runs on Vax and Alpha there are More details at: 
    http://www.axent.com/product/classic/kblock1.htm
   
   Looks like they are using XautoLock (but from a 3rd party?) 

    Also Braintree's Vigil product info is available at:

    http://www.braintree.co.uk/BT_VIGIL.HTM


                                          - Leo