From: Steve Pitchers <qiashuchuc@kr...> - 2006-01-13 17:50:34
Does anyone have a good solution to avoid altering the access time on =20
files that have not changed since the last backup. I know there is an =20
option for (attempting to) restore the old access time, but that alters =20
the change time, which is even worse for our situation.
What about an option to faubackup-find that sends only files that have =20
changed since a specified timestamp file has been modified? Would any =20
problems arise from sending only a subset of files? I imagine there woul=
be a need to send a record of filename and inode number even if the =20
contents of the file are identical in order to make the MACHINE:DIR tree =
look right. Is that the case?
Get latest updates about Open Source Projects, Conferences and News.