</term>
<listitem>
<para>
- Set the number of days since January 1st, 1970 when the password
+ Set the number of days since 1970-01-01 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 <replaceable>LAST_DAY</replaceable> is set to
</term>
<listitem>
<para>
- Set the date or number of days since January 1, 1970 on which the
+ Set the date or number of days since 1970-01-01 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
in 180 days:
</para>
<programlisting>
- chage -E $(date -d +180days +%Y-%m-%d)
+ chage -E $(date -d +180days +%F)
</programlisting>
<para>
Passing the number <emphasis remap='I'>-1</emphasis> as the
still be able to login using another authentication token
(e.g. an SSH key). To disable the account, administrators
should use <command>usermod --expiredate 1</command> (this sets
- the account's expire date to Jan 2, 1970).
+ the account's expire date to 1970-01-02).
</para>
<para>
Users with a locked password are not allowed to change their
<listitem>
<para>
The date of the last password change, expressed as the number
- of days since Jan 1, 1970 00:00 UTC.
+ of days since 1970-01-01 00:00:00 UTC.
</para>
<para>
The value 0 has a special meaning, which is that the user
<listitem>
<para>
The date of expiration of the account, expressed as the number
- of days since Jan 1, 1970 00:00 UTC.
+ of days since 1970-01-01 00:00:00 UTC.
</para>
<para>
Note that an account expiration differs from a password