Merge pull request #310 from ikerexxe/upstream_man_clarifications
Man clarifications
This commit is contained in:
commit
c0818ab01d
@ -102,6 +102,9 @@
|
|||||||
Set the number of days since January 1st, 1970 when the password
|
Set the number of days since January 1st, 1970 when the password
|
||||||
was last changed. The date may also be expressed in the format
|
was last changed. The date may also be expressed in the format
|
||||||
YYYY-MM-DD (or the format more commonly used in your area).
|
YYYY-MM-DD (or the format more commonly used in your area).
|
||||||
|
If the <replaceable>LAST_DAY</replaceable> is set to
|
||||||
|
<emphasis>0</emphasis> the user is forced to change his password
|
||||||
|
on the next log on.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
@ -118,6 +121,13 @@
|
|||||||
contact the system administrator before being able to use the
|
contact the system administrator before being able to use the
|
||||||
system again.
|
system again.
|
||||||
</para>
|
</para>
|
||||||
|
<para>
|
||||||
|
For example the following can be used to set an account to expire
|
||||||
|
in 180 days:
|
||||||
|
</para>
|
||||||
|
<programlisting>
|
||||||
|
chage -E $(date -d +180days +%Y-%m-%d)
|
||||||
|
</programlisting>
|
||||||
<para>
|
<para>
|
||||||
Passing the number <emphasis remap='I'>-1</emphasis> as the
|
Passing the number <emphasis remap='I'>-1</emphasis> as the
|
||||||
<replaceable>EXPIRE_DATE</replaceable> will remove an account
|
<replaceable>EXPIRE_DATE</replaceable> will remove an account
|
||||||
@ -239,6 +249,18 @@
|
|||||||
The <command>chage</command> program requires a shadow password file to
|
The <command>chage</command> program requires a shadow password file to
|
||||||
be available.
|
be available.
|
||||||
</para>
|
</para>
|
||||||
|
<para>
|
||||||
|
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.
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
The <command>chage</command> program will also not report any
|
||||||
|
inconsistency between the shadow and passwd files (e.g. missing x in
|
||||||
|
the passwd file). The <command>pwck</command> can be used to check
|
||||||
|
for this kind of inconsistencies.
|
||||||
|
</para>
|
||||||
<para>The <command>chage</command> command is restricted to the root
|
<para>The <command>chage</command> command is restricted to the root
|
||||||
user, except for the <option>-l</option> option, which may be used by
|
user, except for the <option>-l</option> option, which may be used by
|
||||||
an unprivileged user to determine when their password or account is due
|
an unprivileged user to determine when their password or account is due
|
||||||
|
@ -334,13 +334,13 @@
|
|||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><replaceable>4</replaceable></term>
|
<term><replaceable>4</replaceable></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>GID not unique (when <option>-o</option> not used)</para>
|
<para>GID is already used (when called without <option>-o</option>)</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><replaceable>9</replaceable></term>
|
<term><replaceable>9</replaceable></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>group name not unique</para>
|
<para>group name is already used</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -299,7 +299,7 @@
|
|||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><replaceable>4</replaceable></term>
|
<term><replaceable>4</replaceable></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>E_GID_IN_USE: specified group doesn't exist</para>
|
<para>E_GID_IN_USE: group id already in use</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -129,7 +129,7 @@
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
The date of the last password change, expressed as the number
|
The date of the last password change, expressed as the number
|
||||||
of days since Jan 1, 1970.
|
of days since Jan 1, 1970 00:00 UTC.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
The value 0 has a special meaning, which is that the user
|
The value 0 has a special meaning, which is that the user
|
||||||
@ -208,8 +208,8 @@
|
|||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
After expiration of the password and this expiration period is
|
After expiration of the password and this expiration period is
|
||||||
elapsed, no login is possible using the current user's
|
elapsed, no login is possible for the user. The user should contact
|
||||||
password. The user should contact her administrator.
|
her administrator.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
An empty field means that there are no enforcement of an
|
An empty field means that there are no enforcement of an
|
||||||
@ -224,7 +224,7 @@
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
The date of expiration of the account, expressed as the number
|
The date of expiration of the account, expressed as the number
|
||||||
of days since Jan 1, 1970.
|
of days since Jan 1, 1970 00:00 UTC.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
Note that an account expiration differs from a password
|
Note that an account expiration differs from a password
|
||||||
|
@ -361,6 +361,11 @@
|
|||||||
<option>CREATE_HOME</option> is not enabled, no home
|
<option>CREATE_HOME</option> is not enabled, no home
|
||||||
directories are created.
|
directories are created.
|
||||||
</para>
|
</para>
|
||||||
|
<para>
|
||||||
|
The directory where the user's home directory is created must
|
||||||
|
exist and have proper SELinux context and permissions. Otherwise
|
||||||
|
the user's home directory cannot be created or accessed.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
|
@ -143,7 +143,8 @@
|
|||||||
If the <option>-m</option>
|
If the <option>-m</option>
|
||||||
option is given, the contents of the current home directory will
|
option is given, the contents of the current home directory will
|
||||||
be moved to the new home directory, which is created if it does
|
be moved to the new home directory, which is created if it does
|
||||||
not already exist.
|
not already exist. If the current home directory does not exist
|
||||||
|
the new home directory will not be created.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
@ -205,6 +206,12 @@
|
|||||||
The group ownership of files outside of the user's home directory
|
The group ownership of files outside of the user's home directory
|
||||||
must be fixed manually.
|
must be fixed manually.
|
||||||
</para>
|
</para>
|
||||||
|
<para>
|
||||||
|
The change of the group ownership of files inside of the user's
|
||||||
|
home directory is also not done if the home dir owner uid is
|
||||||
|
different from the current or new user id. This is a safety measure
|
||||||
|
for special home directories such as <filename>/</filename>.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
@ -267,7 +274,8 @@
|
|||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Move the content of the user's home directory to the new
|
Move the content of the user's home directory to the new
|
||||||
location.
|
location. If the current home directory does not exist
|
||||||
|
the new home directory will not be created.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
This option is only valid in combination with the
|
This option is only valid in combination with the
|
||||||
@ -380,6 +388,12 @@
|
|||||||
The ownership of files outside of the user's home directory
|
The ownership of files outside of the user's home directory
|
||||||
must be fixed manually.
|
must be fixed manually.
|
||||||
</para>
|
</para>
|
||||||
|
<para>
|
||||||
|
The change of the user ownership of files inside of the user's
|
||||||
|
home directory is also not done if the home dir owner uid is
|
||||||
|
different from the current or new user id. This is a safety measure
|
||||||
|
for special home directories such as <filename>/</filename>.
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
No checks will be performed with regard to the
|
No checks will be performed with regard to the
|
||||||
<option>UID_MIN</option>, <option>UID_MAX</option>,
|
<option>UID_MIN</option>, <option>UID_MAX</option>,
|
||||||
|
Loading…
Reference in New Issue
Block a user