Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utah.edu!zeleznik
From: zeleznik%cs.utah.edu@wasatch.utah.edu (Mike Zeleznik)
Newsgroups: comp.sys.apollo
Subject: Re: WBAK/OmniBack mod/create times
Message-ID: <3192@wasatch.utah.edu>
Date: 24 Aug 89 02:13:14 GMT
References: <3188@wasatch.utah.edu>
Sender: news@wasatch.utah.edu
Distribution: world
Organization: University of Utah CS Dept
Lines: 26
Keywords: backup archive wbak rbak omniback

In article <3188@wasatch.utah.edu> zeleznik%cs.utah.edu@wasatch.utah.edu (Mike Zeleznik) writes:
>Is there a good reason why wbak uses the mod time of a file instead of its
>create time for incrementals?  
>

Please note: I realize mod time is the logical choice by its name.  Create
time just seemed to catch more common changes in the files than mod time.
From what I have seen, both create and mod time are reset on append and on
edit, but create time will also catch the previously mentioned common
situations that mod time misses.

However, as was pointed out, there are some things create time will miss
(e.g., in place mods).

Does mod time really end up catching more of the more common changes?

Would you really need to use both to be sure of catching all changes?

Thanks,
Mike

  Michael Zeleznik              Computer Science Dept.
                                University of Utah
  zeleznik@cs.utah.edu          Salt Lake City, UT  84112
                                (801) 581-5617