On Tuesday, December 21, 2004 10:33:03 -0700 "Kristen J. Webb" <[EMAIL PROTECTED]> wrote:
It appears that there may be more issues related to the display of the Last Update field
1.3 output:
Creation Sun Dec 19 06:50:29 1999 Copy Fri Oct 31 12:09:16 2003 Backup Wed Dec 15 15:11:18 2004 Last Update Wed Jul 14 06:13:18 1999
1.2 output:
Creation Sun Dec 19 06:50:29 1999 Last Update Sun Dec 19 06:50:29 1999
In the 1.3 output the last update is older than the creation date in this example.
It seems that it should be the same as the Creation date or Never in this instance.
If you were parsing the output of "vos examine" to see when a volume was modified in 1.2, then you are going to be unhappy some of the time.
You see, volumes have something like 5 or 6 different timestamps. If you're doing an incremental dump, then the one you want is the one printed by 1.3 as the "last update" stamp. In certain circumstances this can be older than the creation stamp, because of what constitutes "creation" of a volume. For example, on a cloned volume this is the date the clone was created, which is always more recent than the last time the source volume was modified.
Unfortunately, in OpenAFS 1.2.x and earlier, vos tries to be "friendly". The number it prints next to "Last Update" is actually the more recent of the creationDate or the updateDate. Starting in 1.3, it will print the actual updateDate, even if it is older than the creationDate.
-- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]> Sr. Research Systems Programmer School of Computer Science - Research Computing Facility Carnegie Mellon University - Pittsburgh, PA
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
