diff options
author | Michael Fenn <fennm@deshawresearch.com> | 2013-05-24 12:11:55 -0400 |
---|---|---|
committer | Michael Fenn <fennm@deshawresearch.com> | 2013-05-24 12:11:55 -0400 |
commit | 6fffddf1cc3e73bf831fb3bbe36c928d1ebb8c77 (patch) | |
tree | db2978e695c602b46c7de5cd7e45843aa798325e /man/bcfg2-reports.8 | |
parent | f1f33a03d25618e680736aaa6bb590ab1f5ac22d (diff) | |
download | bcfg2-6fffddf1cc3e73bf831fb3bbe36c928d1ebb8c77.tar.gz bcfg2-6fffddf1cc3e73bf831fb3bbe36c928d1ebb8c77.tar.bz2 bcfg2-6fffddf1cc3e73bf831fb3bbe36c928d1ebb8c77.zip |
Cfg: Handle bogus created events as changed
It is possible for the FAM (gamin in particular) to send a created
event for a file that already exists if the file is updated in a
particular way. I suppose that the event is technically correct
since a new inode really was created, but the file is only changed
from bcfg2's point of view.
For instance, the "atomic" copy-to-temp-then-move-over-top method
that rsync uses will expose this behavior. Example:
rsync -a --temp-dir=/var/tmp --delete-after \
--exclude Packages/cache --exclude Packages/keys \
--exclude Reporting/DirectStore --exclude probed.xml \
/var/lib/bcfg2/ $OTHERSERVER:/var/lib/bcfg2
Diffstat (limited to 'man/bcfg2-reports.8')
0 files changed, 0 insertions, 0 deletions