summaryrefslogtreecommitdiff
path: root/Utility
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-06-20 19:04:16 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-06-20 19:29:53 -0400
commit33b914bcf1f277aecccb4194e296f17f4708e434 (patch)
tree0995105b30ef3d3508761d80b0091e7d9545d659 /Utility
parente0fdfb2e706da2cb1451193c658dc676b0530968 (diff)
pending adds now retried for kqueue
Rethought how to keep track of pending adds that need to be retried later. The commit thread already run up every second when there are changes, so let's keep pending adds queued as changes until they're safe to add. Also, the committer is now smarter about avoiding empty commits when all the adds are currently unsafe, or in the rare case that an add event for a symlink is not received in time. It may avoid them entirely. This seems to work as before for inotify, and is untested for kqueue. (Actually commit batching seems to be improved for inotify, although I'm not sure why. I'm seeing only two commits made during large batch operations, and the first of those is the non-batch mode commit.)
Diffstat (limited to 'Utility')
0 files changed, 0 insertions, 0 deletions