summaryrefslogtreecommitdiffstats
path: root/upstream/fedora-rawhide/man5/integritytab.5
diff options
context:
space:
mode:
Diffstat (limited to 'upstream/fedora-rawhide/man5/integritytab.5')
-rw-r--r--upstream/fedora-rawhide/man5/integritytab.59
1 files changed, 3 insertions, 6 deletions
diff --git a/upstream/fedora-rawhide/man5/integritytab.5 b/upstream/fedora-rawhide/man5/integritytab.5
index 1272444a..d29162af 100644
--- a/upstream/fedora-rawhide/man5/integritytab.5
+++ b/upstream/fedora-rawhide/man5/integritytab.5
@@ -1,5 +1,5 @@
'\" t
-.TH "INTEGRITYTAB" "5" "" "systemd 255" "integritytab"
+.TH "INTEGRITYTAB" "5" "" "systemd 256~rc3" "integritytab"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@@ -81,7 +81,7 @@ Added in version 250\&.
.PP
\fBmode=(journal|bitmap|direct)\fR
.RS 4
-Enable journaled, bitmapped or direct (passthrough) mode\&. Journaled mode is the default when this option is not specified\&. It provides safety against crashes, but can be slow because all data has to be written twice\&. Bitmap mode is more efficient since it requires only a single write, but it is less reliable because if data corruption happens when the machine crashes, it may not be detected\&. Direct mode disables the journal and the bitmap\&. Corresponds to the "direct writes" mode documented in
+Enable journaled, bitmapped or direct (passthrough) mode\&. Journaled mode is the default when this option is not specified\&. It provides safety against crashes, but can be slow because all data has to be written twice\&. Bitmap mode is more efficient since it requires only a single write, but it is less reliable because if data corruption happens when the machine crashes, it might not be detected\&. Direct mode disables the journal and the bitmap\&. Corresponds to the "direct writes" mode documented in
\m[blue]\fBthe dm\-integrity documentation\fR\m[]\&\s-2\u[1]\d\s+2\&. Note that without a journal, if there is a crash, it is possible that the integrity tags and data will not match\&. If used, the journal\-* options below will have no effect if passed\&.
.sp
Added in version 254\&.
@@ -177,10 +177,7 @@ home PARTUUID=4973d0b8\-1b15\-c449\-96ec\-94bab7f6a7b8 /etc/hmac\&.key
.\}
.SH "SEE ALSO"
.PP
-\fBsystemd\fR(1),
-\fBsystemd-integritysetup@.service\fR(8),
-\fBsystemd-integritysetup-generator\fR(8),
-\fBintegritysetup\fR(8),
+\fBsystemd\fR(1), \fBsystemd-integritysetup@.service\fR(8), \fBsystemd-integritysetup-generator\fR(8), \fBintegritysetup\fR(8)
.SH "NOTES"
.IP " 1." 4
the dm-integrity documentation