Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucbcad!zen!ucbvax!sdcsvax!ucsdhub!hp-sdd!ncr-sd!crash!telesoft!bruceb
From: bruceb@telesoft.UUCP (Bruce Bergman @spot)
Newsgroups: comp.os.vms
Subject: re: Thanx! (Last LOGIN date vs. file modification date)
Message-ID: <525@telesoft.UUCP>
Date: Tue, 29-Sep-87 20:52:23 EDT
Article-I.D.: telesoft.525
Posted: Tue Sep 29 20:52:23 1987
Date-Received: Sun, 4-Oct-87 21:38:35 EDT
References: <8709291030.AA13927@ucbvax.Berkeley.EDU>
Organization: TeleSoft, San Diego, CA
Lines: 28

In article <8709291030.AA13927@ucbvax.Berkeley.EDU>, (Jerry) writes:
> You should instead use a file that the user is not likely to touch.  The
> easiest thing to do is to create a 0-length file in the user's SYS$LOGIN
> directory, with a name like "LAST.LOGIN".  Teach your users to leave this
> file alone.  (If they screw around with it, they will only be hurting them-
> selves...the system-wide login file would re-create LAST.LOGIN if it found
> that it didn't exist, and of course display NOTICE.TXT.)
> 
> 							-- Jerry
> ------

How about using the root level directory for that user?  It's likely to
never change over the course of a user's life, and it's pretty easy to
determine which filename we're talking about ([000000]'name'.DIR;).

Just a thought.

Bruce bergman
-- 
allegra!\                         TeleSoft, Inc.
gould9!  \      crash!--\         (619) 457-2700 x123
ihnp4!    \              \
           >--sdcsvax!---->--telesoft!bruceb (Bruce Bergman N7HAW)
nosc!     /              /
scgvaxd! /     log-hb!--/         5959 Cornerstone Court West
ucbvax! /                         San Diego, CA.  92121-9891

All expressed opinions belong to "Bill the Cat" or me.  :^)