Blame SOURCES/bz1818983-gfs2_5_Update_some_mentions_of_gfs2_tool.patch

9757e7
commit 6a5d984b2d5deb989faae2ce567e886b400f257d
9757e7
Author: Andrew Price <anprice@redhat.com>
9757e7
Date:   Tue Apr 7 15:25:06 2020 +0100
9757e7
9757e7
    gfs2.5: Update some mentions of gfs2_tool
9757e7
    
9757e7
    Resolves: rhbz#1818983
9757e7
    Signed-off-by: Andrew Price <anprice@redhat.com>
9757e7
9757e7
diff --git a/gfs2/man/gfs2.5 b/gfs2/man/gfs2.5
9757e7
index 436abc09..8f67ce23 100644
9757e7
--- a/gfs2/man/gfs2.5
9757e7
+++ b/gfs2/man/gfs2.5
9757e7
@@ -48,7 +48,7 @@ currently these are \fIlock_nolock\fR and \fIlock_dlm\fR.
9757e7
 
9757e7
 The default lock protocol name is written to disk initially when creating the
9757e7
 filesystem with \fBmkfs.gfs2\fP(8), -p option.  It can be changed on-disk by
9757e7
-using the \fBgfs2_tool\fP(8) utility's \fBsb proto\fP command.
9757e7
+using the \fBtunegfs2\fP(8) command.
9757e7
 
9757e7
 The \fBlockproto\fP mount option should be used only under special
9757e7
 circumstances in which you want to temporarily use a different lock protocol
9757e7
@@ -70,7 +70,7 @@ The format of \fILockTableName\fR is lock-module-specific.  For
9757e7
 
9757e7
 The default cluster/filesystem name is written to disk initially when creating
9757e7
 the filesystem with \fBmkfs.gfs2\fP(8), -t option.  It can be changed on-disk
9757e7
-by using the \fBgfs2_tool\fP(8) utility's \fBsb table\fP command.
9757e7
+by using the \fBtunegfs2\fP(8) command.
9757e7
 
9757e7
 The \fBlocktable\fP mount option should be used only under special
9757e7
 circumstances in which you want to mount the filesystem in a different cluster,