add: Improved detection of files that are modified while being added.
In indirect mode, now checks the inode cache to detect changes to a file. Note that a file can still be changed if a process has it open for write, after landing in the annex. In direct mode, some checking of the inode cache was done before, but from a much later point, so fewer modifications could be detected. Now it's as good as indirect mode. On crippled filesystems, no lock down is done before starting to add a file, so checking the inode cache is the only protection we have.
This commit is contained in:
parent
a52f8f382b
commit
7ce30b534f
6 changed files with 50 additions and 27 deletions
|
@ -7,6 +7,8 @@
|
|||
|
||||
module Types.KeySource where
|
||||
|
||||
import Utility.InodeCache
|
||||
|
||||
{- When content is in the process of being added to the annex,
|
||||
- and a Key generated from it, this data type is used.
|
||||
-
|
||||
|
@ -16,10 +18,12 @@ module Types.KeySource where
|
|||
- for checking. The migrate command uses the content
|
||||
- of a different Key.
|
||||
-
|
||||
-
|
||||
- The inodeCache can be used to detect some types of modifications to
|
||||
- files that may be made while they're in the process of being added.
|
||||
-}
|
||||
data KeySource = KeySource
|
||||
{ keyFilename :: FilePath
|
||||
, contentLocation :: FilePath
|
||||
, inodeCache :: Maybe InodeCache
|
||||
}
|
||||
deriving (Show)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue