On Wed, Oct 08, 2008 at 11:14:56AM -0400, George Sinclair wrote:
> Well, it certainly does see any newly created files, or directory names  
> or modified files, but my observation is that it ignores files whose  
> file status times are not newer, even if they've been moved. When a  
> file's mod time changes, so does its file status time, but not  
> necessarily vice versa. Now obviously, moving these to another server,  
> or another file system on the same server, would affect those times,  
> however, since that's a copy and not an actual (atomic) move. Ditto for  
> recovered data (tar, unzip, NW recover, whatever ...) as the file status  
> times will be the time that the file was written to disk even though its  
> mod time may be older (original).

Right.  The only way around this is for the client to have more
information than just the timestamp of the last backup (or last relevant
backup) and the timestamp(s) of the file.

Without the client seeing the whole index, it can't know that there's
any reason to transmit the data about the files present back to the
server.

-- 
Darren

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER