> -----Original Message-----
> From: VANCE,JEFF (HP-Cupertino,ex1) [mailto:[log in to unmask]]
[...]
> So your idea of not only counting the number of times the same
> user.acct logs on, but also tracking their IP address is sound.
> One idea (not tested at all) is:
> 
> # Test if this user.acct session is already logged on
> # This user.acct is not logged on, check IP address under 
> different user
> # Note: each session's IP address is kept under /usr/ip/xx.xx.xx.xx
>    # build the IP addr file to capture this user's IP address
>    build /tmp/ip/!hpremipaddr;rec=-1,,f,ascii;disc=1
> ...

The only fly-in-the-ointment I see is how does this file "go away" when you log off?  If you rely on a BYE udc, you could get into situations where a user gets ABORTed, but the file would still be left around, and thus the user couldn't [legitimately] log back on.

Secondly, what about "aggregators" [also known as "NAT"'s] where several users are funneled through the same [external to them] IP address [such as putting a remote office on a DSL line...]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *