From 97c26c1924b076ef23ebe4381558e8aa025712b2 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 16:54:37 +0200 Subject: Adding upstream version 1:4.13+dfsg1. Signed-off-by: Daniel Baumann --- man/chage.1.xml | 326 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 326 insertions(+) create mode 100644 man/chage.1.xml (limited to 'man/chage.1.xml') diff --git a/man/chage.1.xml b/man/chage.1.xml new file mode 100644 index 0000000..055c1ed --- /dev/null +++ b/man/chage.1.xml @@ -0,0 +1,326 @@ + + + + +]> + + + + + Julianne Frances + Haugh + Creation, 1990 + + + Thomas + Kłoczko + kloczek@pld.org.pl + shadow-utils maintainer, 2000 - 2007 + + + Nicolas + François + nicolas.francois@centraliens.net + shadow-utils maintainer, 2007 - now + + + + chage + 1 + User Commands + shadow-utils + &SHADOW_UTILS_VERSION; + + + chage + change user password expiry information + + + + chage + + options + + + LOGIN + + + + + + DESCRIPTION + + The chage command changes the number of days between + password changes and the date of the last password change. This + information is used by the system to determine when a user must change + their password. + + + + + OPTIONS + + The options which apply to the chage command are: + + + + + ,  LAST_DAY + + + + Set the number of days since January 1st, 1970 when the password + was last changed. The date may also be expressed in the format + YYYY-MM-DD (or the format more commonly used in your area). + If the LAST_DAY is set to + 0 the user is forced to change his password + on the next log on. + + + + + + ,  EXPIRE_DATE + + + + Set the date or number of days since January 1, 1970 on which the + user's account will no longer be accessible. The date may also + be expressed in the format YYYY-MM-DD (or the format more + commonly used in your area). A user whose account is locked must + contact the system administrator before being able to use the + system again. + + + For example the following can be used to set an account to expire + in 180 days: + + + chage -E $(date -d +180days +%Y-%m-%d) + + + Passing the number -1 as the + EXPIRE_DATE will remove an account + expiration date. + + + + + , + + Display help message and exit. + + + + , + + When printing dates, use YYYY-MM-DD format. + + + + + ,  INACTIVE + + + + Set the number of days of inactivity after a password has + expired before the account is locked. The + INACTIVE option is the number of days + of inactivity. A user whose account is locked must contact the + system administrator before being able to use the system again. + + + Passing the number -1 as the + INACTIVE will remove an account's + inactivity. + + + + + + , + + + + Show account aging information. + + + + + + ,  MIN_DAYS + + + + Set the minimum number of days between password changes to + MIN_DAYS. A value of zero for this field + indicates that the user may change their password at any time. + + + + + + ,  MAX_DAYS + + + + Set the maximum number of days during which a password is valid. + When MAX_DAYS plus + LAST_DAY is less than the current + day, the user will be required to change their password before + being able to use their account. This occurrence can be planned for + in advance by use of the option, which + provides the user with advance warning. + + + Passing the number -1 as + MAX_DAYS will remove checking a + password's validity. + + + + + + ,  CHROOT_DIR + + + + Apply changes in the CHROOT_DIR + directory and use the configuration files from the + CHROOT_DIR directory. + Only absolute paths are supported. + + + + + + ,  WARN_DAYS + + + + Set the number of days of warning before a password change is + required. The WARN_DAYS option is the + number of days prior to the password expiring that a user will + be warned their password is about to expire. + + + + + + If none of the options are selected, chage operates + in an interactive fashion, prompting the user with the current values + for all of the fields. Enter the new value to change the field, or + leave the line blank to use the current value. The current value is + displayed between a pair of [ ] marks. + + + + NOTE + + The chage program requires a shadow password file to + be available. + + + The chage program will report only the information from the shadow + password file. This implies that configuration from other sources + (e.g. LDAP or empty password hash field from the passwd file) that + affect the user's login will not be shown in the chage output. + + + The chage program will also not report any + inconsistency between the shadow and passwd files (e.g. missing x in + the passwd file). The pwck can be used to check + for this kind of inconsistencies. + + The chage command is restricted to the root + user, except for the option, which may be used by + an unprivileged user to determine when their password or account is due + to expire. + + + + + CONFIGURATION + + The following configuration variables in + /etc/login.defs change the behavior of this + tool: + + + &USE_TCB; + + + + + FILES + + + + /etc/passwd + + + User account information. + + + + + /etc/shadow + + + Secure user account information. + + + + + + + EXIT VALUES + + The chage command exits with the following values: + + + 0 + + success + + + + 1 + + permission denied + + + + 2 + + invalid command syntax + + + + 15 + + can't find the shadow password file + + + + + + + + SEE ALSO + + + passwd5 + , + + shadow5 + . + + + -- cgit v1.2.3