Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!aurora!labrea!decwrl!sun!imagen!atari!portal!cup.portal.com!Larry_J_Osterman
From: Larry_J_Osterman@cup.portal.com
Newsgroups: comp.os.vms
Subject: How do you detect login/logout?
Message-ID: <1331@cup.portal.com>
Date: Sat, 7-Nov-87 04:52:46 EST
Article-I.D.: cup.1331
Posted: Sat Nov  7 04:52:46 1987
Date-Received: Wed, 11-Nov-87 01:18:41 EST
References: <8711042320.AA05380@ucbvax.Berkeley.EDU>
Organization: The Portal System (TM)
Lines: 21
XPortal-User-Id: 1.1001.2219


Forgive me if this has been discussed here before, I don't remember it if so.

We need to detect when a user logs in and out without having the user execute
something in login.com or sylogin.com.  The best we've done so far is have
sylogin run a program which writes a mailbox to tell us that a new user is
logging in.  Then the login program locks a resource using an exclusive lock.
The monitoring program (the reader of the mailbox) then attempts to enqueue
a lock on that same resource, specifying an ast be invoked when the lock is
granted.  Since the login program has an exclusive lock, the ast doesn't
get invoked until the user logs out.

This scheme forces us to execute something at login time, but at least we don't
have to execute something at logout time (which we have much less control over
than at login).  But we sure would like to find some way to detect BOTH login
and logout without any action on the new user's part.

Any help would be greatly appreciated.

Larry Osterman
larry_j_osterman@cup.portal.com
sun!cup.portal.com!larry_j_osterman