summaryrefslogtreecommitdiff
path: root/metastore.txt
diff options
context:
space:
mode:
authorAdam Spragg <adam@spra.gg>2022-05-16 14:25:16 +0100
committerAdam Spragg <adam@spra.gg>2022-05-18 17:19:40 +0100
commit96df5969b11b9a64f95c0c28347154b06cfc9d15 (patch)
treed6e7caa88adb474e32acc4992dc1787b12e88878 /metastore.txt
parent0ae5e697e83fef2f200dfdcf16caebc8a15a9681 (diff)
Add -r/--format option to pick the format to save as
Only version 0 is supported here.
Diffstat (limited to 'metastore.txt')
-rw-r--r--metastore.txt24
1 files changed, 16 insertions, 8 deletions
diff --git a/metastore.txt b/metastore.txt
index 7edb5a8..f3d7d55 100644
--- a/metastore.txt
+++ b/metastore.txt
@@ -9,11 +9,11 @@ SYNOPSIS
metastore ACTION [OPTION...] [PATH...]
DESCRIPTION
- Stores or restores metadata (owner, group, permissions, xattrs and
- optionally mtime) for a filesystem tree. This can be used to preserve
- the metadata in situations where it is usually not stored (git and tar
- for example) or as a tripwire like mechanism to detect any changes to
- metadata. Note that e.g. SELinux stores its labels in xattrs so care
+ Stores or restores metadata (owner, group, permissions, xattrs and op‐
+ tionally mtime) for a filesystem tree. This can be used to preserve the
+ metadata in situations where it is usually not stored (git and tar for
+ example) or as a tripwire like mechanism to detect any changes to meta‐
+ data. Note that e.g. SELinux stores its labels in xattrs so care
should be taken when applying stored metadata to make sure that system
security is not compromised.
@@ -72,13 +72,21 @@ OPTIONS
Causes the metadata to be saved, read from the specified file
rather than ./.metadata.
+ -r <foRmat>, --format <foRmat>
+ Causes the metadata to be saved in format <foRmat>. See FORMATS
+ below.
+
PATHS
- If no path is specified, metastore will use the current directory as
- the basis for the actions. This is the recommended way of executing
- metastore. Alternatively, one or more paths can be specified and they
+ If no path is specified, metastore will use the current directory as
+ the basis for the actions. This is the recommended way of executing
+ metastore. Alternatively, one or more paths can be specified and they
will each be examined. Later invocations should be made using the exact
same paths to ensure that the stored metadata is interpreted correctly.
+FORMATS
+ 0 The original and default format, it is a compact binary repre‐
+ sentation of the file metadata stored.
+
AUTHORS
metastore was created by David Härdeman in 2007-2008. Now it is main‐
tained by Przemysław Pawełczyk. All source code contributors are