A file change log tracks changes to the namespace (files and directories) of a file system. Depending on the implementation, a file change log will record changes such as creates, links, unlinks (deletions), renamed files, data changes, and metadata changes (for example, ACLs and permissions). A file change log can be accessed as a file in the file system, or hidden and accessed only programmatically. A file change log differs from a file system's journal.

PropertyValue
dbpprop:abstract
  • A file change log tracks changes to the namespace (files and directories) of a file system. Depending on the implementation, a file change log will record changes such as creates, links, unlinks (deletions), renamed files, data changes, and metadata changes (for example, ACLs and permissions). A file change log can be accessed as a file in the file system, or hidden and accessed only programmatically. A file change log differs from a file system's journal. Such a log can serve at least two purposes. First, some applications must scan an entire file system to discover changes since their last scan. By reading a file change log, they can avoid this scan. Scanning applications include backup utilities, web crawler, search engines, and replication programs. Second, the log can serve as an audit record for activity in a file system.
dbpprop:hasPhotoCollection
rdf:type
rdfs:comment
  • A file change log tracks changes to the namespace (files and directories) of a file system. Depending on the implementation, a file change log will record changes such as creates, links, unlinks (deletions), renamed files, data changes, and metadata changes (for example, ACLs and permissions). A file change log can be accessed as a file in the file system, or hidden and accessed only programmatically. A file change log differs from a file system's journal.
rdfs:label
  • File change log
owl:sameAs
skos:subject
foaf:page
is dbpprop:redirect of
is owl:sameAs of