From bcc701b0e0833aff6fbfaadd19183daa97852ac5 Mon Sep 17 00:00:00 2001 From: Elaine Fonaro Date: Thu, 2 Jun 2022 15:30:38 -0300 Subject: [PATCH] Password command usage is incorrect. (CP r6, dsr6) Updated the original command: removed the from command. Minor edits and also removed the from the comment. Signed-off-by: Elaine Fonaro Change-Id: I876281ef2ddbea9b5df271cc1370b3580277d01e --- .../password-recovery-for-linux-user-accounts.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/source/security/kubernetes/password-recovery-for-linux-user-accounts.rst b/doc/source/security/kubernetes/password-recovery-for-linux-user-accounts.rst index 26a40fc2c..798558b29 100644 --- a/doc/source/security/kubernetes/password-recovery-for-linux-user-accounts.rst +++ b/doc/source/security/kubernetes/password-recovery-for-linux-user-accounts.rst @@ -23,13 +23,13 @@ this type of account as follows: .. code-block:: none - $ sudo passwd + $ sudo passwd $ sudo chage -d 0 -where is the user name of the account to be reset \(for, example, -**sysadmin**\) and is a temporary password. The -:command:`chage` command forces immediate expiration, so that the user must -change the password at first login. +where `` is the user name of the account to be reset \(for, example, +**sysadmin**\) and :command:`sudo passwd ` will prompt for the new +password. The :command:`chage` command forces immediate expiration, so that +the user must change the password at first login. If no other Linux system user accounts have been created, you can recover using the default LDAP **operator** or **admin** accounts. For more