On Fri, 6 Jul 2001 12:46:10 -0400, [log in to unmask] wrote:
[...]
>Furthermore, if it is any kind of file at all, I want to know when a file
>of that name was created. Period. I realize there is NO GOOD way around
>this, if someone purges the file first. But I would want to know how long a
>binary, a work file, an IMAGE file, ANY file, has lived on my system, and
>when it was last modified, and when it was last accessed, for the reasons
>given. [...]
>
>As it is, I would have to work around MPE's way of handling file times.
>Much of this, I can live with and work around. It's a fundamental part of
>the OS, so I do not expect it to change. But I have wished more than once
>that it could change, or at least be much, much easier. And this little
>nit is pretty much the only thing I do not like about MPE, perhaps because
>I have little hope of it being remedied. There are things I don't like,
>like the less than complete integration of HFS / POSIX and MPE / CI, but I
>think that could be remedied.
I don't know if this qualifies as a "good way" around your first problem
mentioned, but it may be a start -- I have a job that runs every night at
or shortly after midnight looking for all files in my account that
were "accessed" on the previous day [yes, this uses MPEX] and places it in
a date-coded filename in a group called "ACCESSED". This gives me a daily
snapshot of what happened on a given day, and to find the "history" of a
given file, I can now use MPEX's print;search= to find all occurances...
%print @.accessed;search=r matches "CCV?818@";PREV="GROUP="
-----Printing A970402.ACCESSED.EMERSON
ACCOUNT= EMERSON GROUP= EXEC
CCVQ818A NMPRG 128W FB 268 268 1 272 2 *
ACCOUNT= EMERSON GROUP= OBJ
CCVQ818A NMOBJ 128W FB 66 4000 1 80 1 8
ACCOUNT= EMERSON GROUP= SOURCE
CCVS818A EDTCT 72B FA 367 367 32 112 1 2
-----Printing A970417.ACCESSED.EMERSON
ACCOUNT= EMERSON GROUP= EXEC
CCVQ818A NMPRG 128W FB 269 269 1 272 2 *
ACCOUNT= EMERSON GROUP= OBJ
CCVQ818A NMOBJ 128W FB 69 4000 1 80 1 8
ACCOUNT= EMERSON GROUP= SOURCE
CCVS818A EDTCT 72B FA 391 391 32 112 1 2
-----Printing A970529.ACCESSED.EMERSON
ACCOUNT= EMERSON GROUP= SOURCE
CCVS818A EDTCT 72B FA 391 391 32 112 1 2 42
-----Printing A981130.ACCESSED.EMERSON
ACCOUNT= EMERSON GROUP= SOURCE
CCVS818B EDTCT 72B FA 400 400 32 128 1 2
-----Printing A981201.ACCESSED.EMERSON
ACCOUNT= EMERSON GROUP= EXEC
CCVQ818B NMPRG 128W FB 267 267 1 272 2 *
ACCOUNT= EMERSON GROUP= OBJ
CCVQ818B NMOBJ 128W FB 70 4000 1 80 1 8
ACCOUNT= EMERSON GROUP= SOURCE
CCVS818B EDTCT 72B FA 406 406 32 128 1 2
-----Printing A990326.ACCESSED.EMERSON
ACCOUNT= EMERSON GROUP= EXEC (CONTINUED)
CCVQ818B NMPRG 128W FB 267 267 1 272 2 *
ACCOUNT= EMERSON GROUP= OBJ
CCVQ818B NMOBJ 128W FB 70 4000 1 80 1 8
ACCOUNT= EMERSON GROUP= SOURCE
CCVS818B EDTCT 72B FA 406 406 32 128 1 2
Although I chose the standard "mode 2" listf, I could have customized the
information logged (say by using FULLNAME, which would include the group)
so I wouldn't have to use PREV= as the above example shows. Also, since
it's not obvious list the MPEX listf,2 headings aren't shown, but on
5/29/1997 I merely "looked at" CCVS818A -- the "42" in the extreme right
column is the "days since modification", so I didn't make any changes on
that day. Likewise, on 11/30 I created 818b, but didn't compile it until
12/01 (I'm somewhat surprised 818a doesn't show "accessed" on 11/30 as it
is likely I had copied 818a to create 818b -- I suspect, then, I used an
MPEX copy to not alter the accdate of the original...)
This has a further advantage in that the file CCVS818A no longer exists:
R:[TOM]/EMERSON/WORK>listf @[log in to unmask],2
MPEX %LISTF @[log in to unmask] PAGE 1
SYSTEM RAVEN TOM.EMERSON,WORK FRI, JUL 6, 2001, 10:15 AM
ACCOUNT= EMERSON GROUP= SOURCE
FILENAME CODE ------------LOGICAL RECORD-------- ----SPACE---- --DAYS--
SIZE TYP EOF LIMIT R/B SECTORS #X MX ACC MOD
CCVS818B EDTCT 72B FA 406 406 32 128 1 2 259 833
which would mean I wouldn't have ANY way of knowing about version 818a
using listf TODAY!
[whups, got a meeting to attend -- I may post more on this later, till
then, consider this "food for thought"]
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
