\fB-D\fR |
[\fB-g\fI group_name \fR]
X.SH DESCRIPTION
-The \fBgroupmems\fR utility allows a user to administer his/her own
+The \fBgroupmems\fR utility allows a user to administer their own
group membership list without the requirement of superuser privileges.
The \fBgroupmems\fR utility is for systems that configure its users to
be in their own name sake primary group (i.e., guest / guest).
# home directories.
# 022 is the default value, but 027, or even 077, could be considered
# for increased privacy. There is no One True Answer here: each sysadmin
-# must make up his/her mind.
+# must make up their mind.
UMASK 022
#
The <command>chage</command> 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
- his/her password.
+ their password.
</para>
</refsect1>
<para>
Set the minimum number of days between password changes to
<replaceable>MIN_DAYS</replaceable>. A value of zero for this field
- indicates that the user may change his/her password at any time.
+ indicates that the user may change their password at any time.
</para>
</listitem>
</varlistentry>
Set the maximum number of days during which a password is valid.
When <replaceable>MAX_DAYS</replaceable> plus
<replaceable>LAST_DAY</replaceable> is less than the current
- day, the user will be required to change his/her password before
- being able to use his/her account. This occurrence can be planned for
+ 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>-W</option> option, which
provides the user with advance warning.
</para>
Set the number of days of warning before a password change is
required. The <replaceable>WARN_DAYS</replaceable> option is the
number of days prior to the password expiring that a user will
- be warned his/her password is about to expire.
+ be warned their password is about to expire.
</para>
</listitem>
</varlistentry>
</para>
<para>The <command>chage</command> command is restricted to the root
user, except for the <option>-l</option> option, which may be used by
- an unprivileged user to determine when his/her password or account is due
+ an unprivileged user to determine when their password or account is due
to expire.
</para>
</refsect1>
<title>DESCRIPTION</title>
<para>
The <command>groupmems</command> command allows a user to administer
- his/her own group membership list without the requirement of
+ their own group membership list without the requirement of
superuser privileges. The <command>groupmems</command> utility is for
systems that configure its users to be in their own name sake primary
group (i.e., guest / guest).
<title>DESCRIPTION</title>
<para>
The <command>passwd</command> command changes passwords for user accounts.
- A normal user may only change the password for his/her own account, while
+ A normal user may only change the password for their own account, while
the superuser may change the password for any account.
<command>passwd</command> also changes the account or associated
password validity period.
<refsect2 id='password_changes'>
<title>Password Changes</title>
<para>
- The user is first prompted for his/her old password, if one is
+ The user is first prompted for their old password, if one is
present. This password is then encrypted and compared against the
stored password. The user has only one chance to enter the correct
password. The superuser is permitted to bypass this step so that
<listitem>
<para>
Immediately expire an account's password. This in effect can
- force a user to change his/her password at the user's next login.
+ force a user to change their password at the user's next login.
</para>
</listitem>
</varlistentry>
<para>
Set the minimum number of days between password changes to
<replaceable>MIN_DAYS</replaceable>. A value of zero for this field
- indicates that the user may change his/her password at any time.
+ indicates that the user may change their password at any time.
</para>
</listitem>
</varlistentry>
Set the number of days of warning before a password change is
required. The <replaceable>WARN_DAYS</replaceable> option is
the number of days prior to the password expiring that a user
- will be warned that his/her password is about to expire.
+ will be warned that their password is about to expire.
</para>
</listitem>
</varlistentry>
#: passwd.1.xml:89(para)
msgid ""
"The <command>passwd</command> command changes passwords for user accounts. A "
-"normal user may only change the password for his/her own account, while the "
+"normal user may only change the password for their own account, while the "
"superuser may change the password for any account. <command>passwd</command> "
"also changes the account or associated password validity period."
msgstr ""
#: passwd.1.xml:99(para)
msgid ""
-"The user is first prompted for his/her old password, if one is present. This "
+"The user is first prompted for their old password, if one is present. This "
"password is then encrypted and compared against the stored password. The "
"user has only one chance to enter the correct password. The superuser is "
"permitted to bypass this step so that forgotten passwords may be changed."
#: passwd.1.xml:207(para)
msgid ""
"Immediately expire an account's password. This in effect can force a user to "
-"change his/her password at the user's next login."
+"change their password at the user's next login."
msgstr ""
"Angiv øjeblikkelig en kontos adgangskode som udløbet. Dette kan tvinge en "
"bruger til at ændre sin adgangskode ved brugerens næste logind."
msgid ""
"Set the minimum number of days between password changes to "
"<replaceable>MIN_DAYS</replaceable>. A value of zero for this field "
-"indicates that the user may change his/her password at any time."
+"indicates that the user may change their password at any time."
msgstr ""
#: passwd.1.xml:291(term)
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned that his/her password is "
+"the password expiring that a user will be warned that their password is "
"about to expire."
msgstr ""
#: groupmems.8.xml:86(para)
msgid ""
-"The <command>groupmems</command> command allows a user to administer his/her "
+"The <command>groupmems</command> command allows a user to administer their "
"own group membership list without the requirement of superuser privileges. "
"The <command>groupmems</command> utility is for systems that configure its "
"users to be in their own name sake primary group (i.e., guest / guest)."
msgid ""
"The <command>chage</command> 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 his/her password."
+"is used by the system to determine when a user must change their password."
msgstr ""
#: chage.1.xml:92(para)
msgid ""
"Set the maximum number of days during which a password is valid. When "
"<replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> "
-"is less than the current day, the user will be required to change his/her "
-"password before being able to use his/her account. This occurrence can be "
+"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>-W</option> option, which "
"provides the user with advance warning."
msgstr ""
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned his/her password is about "
+"the password expiring that a user will be warned their password is about "
"to expire."
msgstr ""
msgid ""
"The <command>chage</command> command is restricted to the root user, except "
"for the <option>-l</option> option, which may be used by an unprivileged "
-"user to determine when his/her password or account is due to expire."
+"user to determine when their password or account is due to expire."
msgstr ""
"Kommandoen <command>chage</command> er begrænset til administratorbrugeren "
"(root), undtaget for tilvalget <option>-l</option>, som kan bruges af en "
#: passwd.1.xml:89(para)
msgid ""
"The <command>passwd</command> command changes passwords for user accounts. A "
-"normal user may only change the password for his/her own account, while the "
+"normal user may only change the password for their own account, while the "
"superuser may change the password for any account. <command>passwd</command> "
"also changes the account or associated password validity period."
msgstr ""
#: passwd.1.xml:99(para)
msgid ""
-"The user is first prompted for his/her old password, if one is present. This "
+"The user is first prompted for their old password, if one is present. This "
"password is then encrypted and compared against the stored password. The "
"user has only one chance to enter the correct password. The superuser is "
"permitted to bypass this step so that forgotten passwords may be changed."
#: passwd.1.xml:207(para)
msgid ""
"Immediately expire an account's password. This in effect can force a user to "
-"change his/her password at the user's next login."
+"change their password at the user's next login."
msgstr ""
"Lässt das Passwort eines Kontos sofort verfallen. Im Ergebnis kann damit "
"erreicht werden, dass ein Benutzer beim nächsten Login das Passwort ändern "
msgid ""
"Set the minimum number of days between password changes to "
"<replaceable>MIN_DAYS</replaceable>. A value of zero for this field "
-"indicates that the user may change his/her password at any time."
+"indicates that the user may change their password at any time."
msgstr ""
"Setzt die Anzahl von Tagen, die mindestens zwischen zwei Änderungen eines "
"Passworts vergehen müssen, auf <replaceable>MIN_TAGE</replaceable>. Ein Wert "
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned that his/her password is "
+"the password expiring that a user will be warned that their password is "
"about to expire."
msgstr ""
"Legt die Anzahl der Tage fest, an denen der Benutzer eine Warnung erhält, "
# SB: 1. I don't understand "sake"? A typo? But of what? 2. I think we shouldn't have the notorious guest account here as an example.
#: groupmems.8.xml:86(para)
msgid ""
-"The <command>groupmems</command> command allows a user to administer his/her "
+"The <command>groupmems</command> command allows a user to administer their "
"own group membership list without the requirement of superuser privileges. "
"The <command>groupmems</command> utility is for systems that configure its "
"users to be in their own name sake primary group (i.e., guest / guest)."
msgid ""
"The <command>chage</command> 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 his/her password."
+"is used by the system to determine when a user must change their password."
msgstr ""
"Der Befehl <command>chage</command> verändert die Anzahl der Tage zwischen "
"dem letzten Wechsel des Passworts und dem nächsten Wechsel. Mit dieser "
msgid ""
"Set the maximum number of days during which a password is valid. When "
"<replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> "
-"is less than the current day, the user will be required to change his/her "
-"password before being able to use his/her account. This occurrence can be "
+"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>-W</option> option, which "
"provides the user with advance warning."
msgstr ""
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned his/her password is about "
+"the password expiring that a user will be warned their password is about "
"to expire."
msgstr ""
"Legt die Anzahl der Tage fest, an denen der Benutzer eine Warnung erhält, "
msgid ""
"The <command>chage</command> command is restricted to the root user, except "
"for the <option>-l</option> option, which may be used by an unprivileged "
-"user to determine when his/her password or account is due to expire."
+"user to determine when their password or account is due to expire."
msgstr ""
"Der Befehl <command>chage</command> kann nur von Root ausgeführt werden. "
"Alle anderen Benutzer können nur die Option <option>-l</option> verwenden, "
#: passwd.1.xml:89(para)
msgid ""
"The <command>passwd</command> command changes passwords for user accounts. A "
-"normal user may only change the password for his/her own account, while the "
+"normal user may only change the password for their own account, while the "
"superuser may change the password for any account. <command>passwd</command> "
"also changes the account or associated password validity period."
msgstr ""
#: passwd.1.xml:99(para)
msgid ""
-"The user is first prompted for his/her old password, if one is present. This "
+"The user is first prompted for their old password, if one is present. This "
"password is then encrypted and compared against the stored password. The "
"user has only one chance to enter the correct password. The superuser is "
"permitted to bypass this step so that forgotten passwords may be changed."
#: passwd.1.xml:207(para)
msgid ""
"Immediately expire an account's password. This in effect can force a user to "
-"change his/her password at the user's next login."
+"change their password at the user's next login."
msgstr ""
"Annuler immédiatement la validité du mot de passe d'un compte. Ceci permet "
"d'obliger un utilisateur à changer son mot de passe lors de sa prochaine "
msgid ""
"Set the minimum number of days between password changes to "
"<replaceable>MIN_DAYS</replaceable>. A value of zero for this field "
-"indicates that the user may change his/her password at any time."
+"indicates that the user may change their password at any time."
msgstr ""
"Définir le nombre minimum de jours entre chaque changement de mot de passe à "
"<replaceable>MIN_DAYS</replaceable>. Une valeur de zéro pour ce champ "
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned that his/her password is "
+"the password expiring that a user will be warned that their password is "
"about to expire."
msgstr ""
"Configurer le nombre de jours d'avertissement avant que le changement de mot "
#: groupmems.8.xml:86(para)
msgid ""
-"The <command>groupmems</command> command allows a user to administer his/her "
+"The <command>groupmems</command> command allows a user to administer their "
"own group membership list without the requirement of superuser privileges. "
"The <command>groupmems</command> utility is for systems that configure its "
"users to be in their own name sake primary group (i.e., guest / guest)."
msgid ""
"The <command>chage</command> 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 his/her password."
+"is used by the system to determine when a user must change their password."
msgstr ""
"La commande <command>chage</command> modifie le nombre de jours entre les "
"changements de mot de passe et la date du dernier changement. Ces "
msgid ""
"Set the maximum number of days during which a password is valid. When "
"<replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> "
-"is less than the current day, the user will be required to change his/her "
-"password before being able to use his/her account. This occurrence can be "
+"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>-W</option> option, which "
"provides the user with advance warning."
msgstr ""
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned his/her password is about "
+"the password expiring that a user will be warned their password is about "
"to expire."
msgstr ""
"Configurer le nombre de jours d'avertissement avant que le changement de mot "
msgid ""
"The <command>chage</command> command is restricted to the root user, except "
"for the <option>-l</option> option, which may be used by an unprivileged "
-"user to determine when his/her password or account is due to expire."
+"user to determine when their password or account is due to expire."
msgstr ""
"La commande <command>chage</command> est réservée à l'utilisateur root, sauf "
"pour l'option <option>-l</option>, qui peut être utilisée par un utilisateur "
#: passwd.1.xml:89(para)
msgid ""
"The <command>passwd</command> command changes passwords for user accounts. A "
-"normal user may only change the password for his/her own account, while the "
+"normal user may only change the password for their own account, while the "
"superuser may change the password for any account. <command>passwd</command> "
"also changes the account or associated password validity period."
msgstr ""
# type: Plain text
#: passwd.1.xml:99(para)
msgid ""
-"The user is first prompted for his/her old password, if one is present. This "
+"The user is first prompted for their old password, if one is present. This "
"password is then encrypted and compared against the stored password. The "
"user has only one chance to enter the correct password. The superuser is "
"permitted to bypass this step so that forgotten passwords may be changed."
#: passwd.1.xml:207(para)
msgid ""
"Immediately expire an account's password. This in effect can force a user to "
-"change his/her password at the user's next login."
+"change their password at the user's next login."
msgstr ""
"Fa scadere subito la password dell'utente. Il che ha l'effetto di forzare un "
"cambio password al successivo accesso da parte dell'utente."
msgid ""
"Set the minimum number of days between password changes to "
"<replaceable>MIN_DAYS</replaceable>. A value of zero for this field "
-"indicates that the user may change his/her password at any time."
+"indicates that the user may change their password at any time."
msgstr ""
"Imposta il numero minimo di giorni tra i cambi di password a "
"<replaceable>MIN_GIORNI</replaceable>. Un valore pari a zero indica che "
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned that his/her password is "
+"the password expiring that a user will be warned that their password is "
"about to expire."
msgstr ""
"Imposta il numero di giorni di preavviso prima che sia obbligatorio cambiare "
#: groupmems.8.xml:86(para)
msgid ""
-"The <command>groupmems</command> command allows a user to administer his/her "
+"The <command>groupmems</command> command allows a user to administer their "
"own group membership list without the requirement of superuser privileges. "
"The <command>groupmems</command> utility is for systems that configure its "
"users to be in their own name sake primary group (i.e., guest / guest)."
msgid ""
"The <command>chage</command> 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 his/her password."
+"is used by the system to determine when a user must change their password."
msgstr ""
"<command>chage</command> modifica il numero minimo di giorni tra i cambi di "
"password e la data dell'ultimo cambio. Queste informazioni sono usate dal "
msgid ""
"Set the maximum number of days during which a password is valid. When "
"<replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> "
-"is less than the current day, the user will be required to change his/her "
-"password before being able to use his/her account. This occurrence can be "
+"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>-W</option> option, which "
"provides the user with advance warning."
msgstr ""
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned his/her password is about "
+"the password expiring that a user will be warned their password is about "
"to expire."
msgstr ""
"Imposta il numero di giorni di preavviso prima che sia obbligatorio cambiare "
msgid ""
"The <command>chage</command> command is restricted to the root user, except "
"for the <option>-l</option> option, which may be used by an unprivileged "
-"user to determine when his/her password or account is due to expire."
+"user to determine when their password or account is due to expire."
msgstr ""
"L'uso del comando <command>chage</command> è permesso solo all'utente root, "
"tranne per l'opzione <option>-l</option>, che può essere usata da un utente "
#: passwd.1.xml:89(para)
msgid ""
"The <command>passwd</command> command changes passwords for user accounts. A "
-"normal user may only change the password for his/her own account, while the "
+"normal user may only change the password for their own account, while the "
"superuser may change the password for any account. <command>passwd</command> "
"also changes the account or associated password validity period."
msgstr ""
#: passwd.1.xml:99(para)
msgid ""
-"The user is first prompted for his/her old password, if one is present. This "
+"The user is first prompted for their old password, if one is present. This "
"password is then encrypted and compared against the stored password. The "
"user has only one chance to enter the correct password. The superuser is "
"permitted to bypass this step so that forgotten passwords may be changed."
#: passwd.1.xml:207(para)
msgid ""
"Immediately expire an account's password. This in effect can force a user to "
-"change his/her password at the user's next login."
+"change their password at the user's next login."
msgstr ""
#: passwd.1.xml:220(term)
msgid ""
"Set the minimum number of days between password changes to "
"<replaceable>MIN_DAYS</replaceable>. A value of zero for this field "
-"indicates that the user may change his/her password at any time."
+"indicates that the user may change their password at any time."
msgstr ""
"Utawia minimalną liczbę dni pomiędzy zmianami hasła na "
"<replaceable>MIN_DAYS</replaceable>. Wartość zerowa oznacza, że użytkownik "
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned that his/her password is "
+"the password expiring that a user will be warned that their password is "
"about to expire."
msgstr ""
#: groupmems.8.xml:86(para)
msgid ""
-"The <command>groupmems</command> command allows a user to administer his/her "
+"The <command>groupmems</command> command allows a user to administer their "
"own group membership list without the requirement of superuser privileges. "
"The <command>groupmems</command> utility is for systems that configure its "
"users to be in their own name sake primary group (i.e., guest / guest)."
msgid ""
"The <command>chage</command> 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 his/her password."
+"is used by the system to determine when a user must change their password."
msgstr ""
"Polecenie <command>chage</command> zmienia liczbę dni pomiędzy zmianami "
"hasła i datę ostatniej zmiany hasła. Informację tę system wykorzystuje do "
msgid ""
"Set the maximum number of days during which a password is valid. When "
"<replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> "
-"is less than the current day, the user will be required to change his/her "
-"password before being able to use his/her account. This occurrence can be "
+"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>-W</option> option, which "
"provides the user with advance warning."
msgstr ""
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned his/her password is about "
+"the password expiring that a user will be warned their password is about "
"to expire."
msgstr ""
"Ustawia na <replaceable>DNI_OSTRZ</replaceable> liczbę dni przed upływem "
msgid ""
"The <command>chage</command> command is restricted to the root user, except "
"for the <option>-l</option> option, which may be used by an unprivileged "
-"user to determine when his/her password or account is due to expire."
+"user to determine when their password or account is due to expire."
msgstr ""
"Polecenia chage może użyć tylko użytkownik root, za wyjątkiem opcji <option>-"
"l</option>. Może się nią posłużyć się użytkownik nieuprzywilejowany do "
#: passwd.1.xml:89(para)
msgid ""
"The <command>passwd</command> command changes passwords for user accounts. A "
-"normal user may only change the password for his/her own account, while the "
+"normal user may only change the password for their own account, while the "
"superuser may change the password for any account. <command>passwd</command> "
"also changes the account or associated password validity period."
msgstr ""
# type: Content of: <refentry><refsect1><refsect2><para>
#: passwd.1.xml:99(para)
msgid ""
-"The user is first prompted for his/her old password, if one is present. This "
+"The user is first prompted for their old password, if one is present. This "
"password is then encrypted and compared against the stored password. The "
"user has only one chance to enter the correct password. The superuser is "
"permitted to bypass this step so that forgotten passwords may be changed."
#: passwd.1.xml:207(para)
msgid ""
"Immediately expire an account's password. This in effect can force a user to "
-"change his/her password at the user's next login."
+"change their password at the user's next login."
msgstr ""
"Немедленно сделать пароль устаревшим. В результате это заставит пользователя "
"изменить пароль при следующем входе в систему."
msgid ""
"Set the minimum number of days between password changes to "
"<replaceable>MIN_DAYS</replaceable>. A value of zero for this field "
-"indicates that the user may change his/her password at any time."
+"indicates that the user may change their password at any time."
msgstr ""
"Задать <replaceable>минимальное количество дней</replaceable> между сменами "
"пароля. Нулевое значение этого поля указывает на то, что пользователь может "
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned that his/her password is "
+"the password expiring that a user will be warned that their password is "
"about to expire."
msgstr ""
"Установить число дней выдачи предупреждения, перед тем как потребуется смена "
#: groupmems.8.xml:86(para)
msgid ""
-"The <command>groupmems</command> command allows a user to administer his/her "
+"The <command>groupmems</command> command allows a user to administer their "
"own group membership list without the requirement of superuser privileges. "
"The <command>groupmems</command> utility is for systems that configure its "
"users to be in their own name sake primary group (i.e., guest / guest)."
msgid ""
"The <command>chage</command> 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 his/her password."
+"is used by the system to determine when a user must change their password."
msgstr ""
"Программа <command>chage</command> изменяет количество дней между датой "
"смены пароля и датой последней смены пароля. Эта информация используется "
msgid ""
"Set the maximum number of days during which a password is valid. When "
"<replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> "
-"is less than the current day, the user will be required to change his/her "
-"password before being able to use his/her account. This occurrence can be "
+"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>-W</option> option, which "
"provides the user with advance warning."
msgstr ""
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned his/her password is about "
+"the password expiring that a user will be warned their password is about "
"to expire."
msgstr ""
"Установить количество дней выдачи предупреждения, перед тем как потребуется "
msgid ""
"The <command>chage</command> command is restricted to the root user, except "
"for the <option>-l</option> option, which may be used by an unprivileged "
-"user to determine when his/her password or account is due to expire."
+"user to determine when their password or account is due to expire."
msgstr ""
"Программа <command>chage</command> работает только от суперпользователя, за "
"исключением вызова с параметром <option>-l</option>, который может "
msgstr ""
#: passwd.1.xml:89(para)
-msgid "The <command>passwd</command> command changes passwords for user accounts. A normal user may only change the password for his/her own account, while the superuser may change the password for any account. <command>passwd</command> also changes the account or associated password validity period."
+msgid "The <command>passwd</command> command changes passwords for user accounts. A normal user may only change the password for their own account, while the superuser may change the password for any account. <command>passwd</command> also changes the account or associated password validity period."
msgstr ""
#: passwd.1.xml:98(title)
msgstr ""
#: passwd.1.xml:99(para)
-msgid "The user is first prompted for his/her old password, if one is present. This password is then encrypted and compared against the stored password. The user has only one chance to enter the correct password. The superuser is permitted to bypass this step so that forgotten passwords may be changed."
+msgid "The user is first prompted for their old password, if one is present. This password is then encrypted and compared against the stored password. The user has only one chance to enter the correct password. The superuser is permitted to bypass this step so that forgotten passwords may be changed."
msgstr ""
#: passwd.1.xml:107(para)
msgstr ""
#: passwd.1.xml:207(para)
-msgid "Immediately expire an account's password. This in effect can force a user to change his/her password at the user's next login."
+msgid "Immediately expire an account's password. This in effect can force a user to change their password at the user's next login."
msgstr ""
#: passwd.1.xml:220(term)
msgstr ""
#: passwd.1.xml:273(para) chage.1.xml:168(para)
-msgid "Set the minimum number of days between password changes to <replaceable>MIN_DAYS</replaceable>. A value of zero for this field indicates that the user may change his/her password at any time."
+msgid "Set the minimum number of days between password changes to <replaceable>MIN_DAYS</replaceable>. A value of zero for this field indicates that the user may change their password at any time."
msgstr ""
#: passwd.1.xml:291(term)
msgstr ""
#: passwd.1.xml:348(para)
-msgid "Set the number of days of warning before a password change is required. The <replaceable>WARN_DAYS</replaceable> option is the number of days prior to the password expiring that a user will be warned that his/her password is about to expire."
+msgid "Set the number of days of warning before a password change is required. The <replaceable>WARN_DAYS</replaceable> option is the number of days prior to the password expiring that a user will be warned that their password is about to expire."
msgstr ""
#: passwd.1.xml:357(term)
msgstr ""
#: groupmems.8.xml:86(para)
-msgid "The <command>groupmems</command> command allows a user to administer his/her own group membership list without the requirement of superuser privileges. The <command>groupmems</command> utility is for systems that configure its users to be in their own name sake primary group (i.e., guest / guest)."
+msgid "The <command>groupmems</command> command allows a user to administer their own group membership list without the requirement of superuser privileges. The <command>groupmems</command> utility is for systems that configure its users to be in their own name sake primary group (i.e., guest / guest)."
msgstr ""
#: groupmems.8.xml:94(para)
msgstr ""
#: chage.1.xml:82(para)
-msgid "The <command>chage</command> 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 his/her password."
+msgid "The <command>chage</command> 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."
msgstr ""
#: chage.1.xml:92(para)
msgstr ""
#: chage.1.xml:180(para)
-msgid "Set the maximum number of days during which a password is valid. When <replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> is less than the current day, the user will be required to change his/her password before being able to use his/her account. This occurrence can be planned for in advance by use of the <option>-W</option> option, which provides the user with advance warning."
+msgid "Set the maximum number of days during which a password is valid. When <replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> 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>-W</option> option, which provides the user with advance warning."
msgstr ""
#: chage.1.xml:189(para)
msgstr ""
#: chage.1.xml:213(para)
-msgid "Set the number of days of warning before a password change is required. The <replaceable>WARN_DAYS</replaceable> option is the number of days prior to the password expiring that a user will be warned his/her password is about to expire."
+msgid "Set the number of days of warning before a password change is required. The <replaceable>WARN_DAYS</replaceable> option is the number of days prior to the password expiring that a user will be warned their password is about to expire."
msgstr ""
#: chage.1.xml:222(para)
msgstr ""
#: chage.1.xml:236(para)
-msgid "The <command>chage</command> command is restricted to the root user, except for the <option>-l</option> option, which may be used by an unprivileged user to determine when his/her password or account is due to expire."
+msgid "The <command>chage</command> command is restricted to the root 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 to expire."
msgstr ""
#: chage.1.xml:301(replaceable)
#, fuzzy
msgid ""
"The <command>passwd</command> command changes passwords for user accounts. A "
-"normal user may only change the password for his/her own account, while the "
+"normal user may only change the password for their own account, while the "
"superuser may change the password for any account. <command>passwd</command> "
"also changes the account or associated password validity period."
msgstr ""
#: passwd.1.xml:99(para)
#, fuzzy
msgid ""
-"The user is first prompted for his/her old password, if one is present. This "
+"The user is first prompted for their old password, if one is present. This "
"password is then encrypted and compared against the stored password. The "
"user has only one chance to enter the correct password. The superuser is "
"permitted to bypass this step so that forgotten passwords may be changed."
#: passwd.1.xml:207(para)
msgid ""
"Immediately expire an account's password. This in effect can force a user to "
-"change his/her password at the user's next login."
+"change their password at the user's next login."
msgstr ""
"Lösenordet för ett konto sätts omedelbart som utgånget. Detta kan tvinga en "
"användare att ändra sitt lösenord vid nästa inloggningsförsök."
msgid ""
"Set the minimum number of days between password changes to "
"<replaceable>MIN_DAYS</replaceable>. A value of zero for this field "
-"indicates that the user may change his/her password at any time."
+"indicates that the user may change their password at any time."
msgstr ""
"Sätter minimalt antal dagar mellan lösenordsändringar till "
"<replaceable>MIN_DAGAR</replaceable>. Ett nollvärde för detta fält betyder "
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned that his/her password is "
+"the password expiring that a user will be warned that their password is "
"about to expire."
msgstr ""
"Sätter antalet dagar för varning före ett lösenord behöver ändras. Flaggan "
#: groupmems.8.xml:86(para)
msgid ""
-"The <command>groupmems</command> command allows a user to administer his/her "
+"The <command>groupmems</command> command allows a user to administer their "
"own group membership list without the requirement of superuser privileges. "
"The <command>groupmems</command> utility is for systems that configure its "
"users to be in their own name sake primary group (i.e., guest / guest)."
msgid ""
"The <command>chage</command> 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 his/her password."
+"is used by the system to determine when a user must change their password."
msgstr ""
#: chage.1.xml:92(para)
msgid ""
"Set the maximum number of days during which a password is valid. When "
"<replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> "
-"is less than the current day, the user will be required to change his/her "
-"password before being able to use his/her account. This occurrence can be "
+"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>-W</option> option, which "
"provides the user with advance warning."
msgstr ""
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned his/her password is about "
+"the password expiring that a user will be warned their password is about "
"to expire."
msgstr ""
msgid ""
"The <command>chage</command> command is restricted to the root user, except "
"for the <option>-l</option> option, which may be used by an unprivileged "
-"user to determine when his/her password or account is due to expire."
+"user to determine when their password or account is due to expire."
msgstr ""
#: chage.1.xml:301(replaceable)
#: passwd.1.xml:89(para)
msgid ""
"The <command>passwd</command> command changes passwords for user accounts. A "
-"normal user may only change the password for his/her own account, while the "
+"normal user may only change the password for their own account, while the "
"superuser may change the password for any account. <command>passwd</command> "
"also changes the account or associated password validity period."
msgstr ""
#: passwd.1.xml:99(para)
msgid ""
-"The user is first prompted for his/her old password, if one is present. This "
+"The user is first prompted for their old password, if one is present. This "
"password is then encrypted and compared against the stored password. The "
"user has only one chance to enter the correct password. The superuser is "
"permitted to bypass this step so that forgotten passwords may be changed."
#: passwd.1.xml:207(para)
msgid ""
"Immediately expire an account's password. This in effect can force a user to "
-"change his/her password at the user's next login."
+"change their password at the user's next login."
msgstr "让一个账户的密码立即过期。这可以强制一个用户下次登录时更改密码。"
#: passwd.1.xml:220(term)
msgid ""
"Set the minimum number of days between password changes to "
"<replaceable>MIN_DAYS</replaceable>. A value of zero for this field "
-"indicates that the user may change his/her password at any time."
+"indicates that the user may change their password at any time."
msgstr ""
"在密码更改之间的最小天数设置为 <replaceable>MIN_DAYS</replaceable>。此字段中"
"的 0 值表示用户可以在任何时间更改其密码。"
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned that his/her password is "
+"the password expiring that a user will be warned that their password is "
"about to expire."
msgstr ""
"设置在要求更改密码之前警告的天数。<replaceable>WARN_DAYS</replaceable> 选项是"
#: groupmems.8.xml:86(para)
msgid ""
-"The <command>groupmems</command> command allows a user to administer his/her "
+"The <command>groupmems</command> command allows a user to administer their "
"own group membership list without the requirement of superuser privileges. "
"The <command>groupmems</command> utility is for systems that configure its "
"users to be in their own name sake primary group (i.e., guest / guest)."
msgid ""
"The <command>chage</command> 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 his/her password."
+"is used by the system to determine when a user must change their password."
msgstr ""
#: chage.1.xml:92(para)
msgid ""
"Set the maximum number of days during which a password is valid. When "
"<replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> "
-"is less than the current day, the user will be required to change his/her "
-"password before being able to use his/her account. This occurrence can be "
+"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>-W</option> option, which "
"provides the user with advance warning."
msgstr ""
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned his/her password is about "
+"the password expiring that a user will be warned their password is about "
"to expire."
msgstr ""
"设置在要求更改密码之前几天开始警告。<replaceable>WARN_DAYS</replaceable> 选项"
msgid ""
"The <command>chage</command> command is restricted to the root user, except "
"for the <option>-l</option> option, which may be used by an unprivileged "
-"user to determine when his/her password or account is due to expire."
+"user to determine when their password or account is due to expire."
msgstr ""
"只有 root 才可以使用 <command>chage</command>，一个特殊情况是 <option>-l</"
"option> 选项，用来让非特权用户觉得自己的密码或账户何时过期。"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append afegeix l'usuari als GRUPS addicionals\n"
" llistats amb la opció -G sense eliminar-los\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append přidá uživatele do dalších SKUPIN zadaných\n"
" volbou -G; neruší členství v ostatních sk.\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append tilføj brugeren til de supplementære "
"GRUPPER\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append Benutzer zu zusätzlichen Gruppen "
"hinzufügen,\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append προσθήκη του χρήστη στις συμπληρωματικές "
"ΟΜΑΔΕΣ\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append gehitu erabiltzailea -G aukerak zehaztutako "
"talde\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
#: passwd.1.xml:89(para)
msgid ""
"The <command>passwd</command> command changes passwords for user accounts. A "
-"normal user may only change the password for his/her own account, while the "
+"normal user may only change the password for their own account, while the "
"superuser may change the password for any account. <command>passwd</command> "
"also changes the account or associated password validity period."
msgstr ""
#: passwd.1.xml:99(para)
msgid ""
-"The user is first prompted for his/her old password, if one is present. This "
+"The user is first prompted for their old password, if one is present. This "
"password is then encrypted and compared against the stored password. The "
"user has only one chance to enter the correct password. The superuser is "
"permitted to bypass this step so that forgotten passwords may be changed."
#: passwd.1.xml:207(para)
msgid ""
"Immediately expire an account's password. This in effect can force a user to "
-"change his/her password at the user's next login."
+"change their password at the user's next login."
msgstr ""
"Annuler immédiatement la validité du mot de passe d'un compte. Ceci permet "
"d'obliger un utilisateur à changer son mot de passe lors de sa prochaine "
msgid ""
"Set the minimum number of days between password changes to "
"<replaceable>MIN_DAYS</replaceable>. A value of zero for this field "
-"indicates that the user may change his/her password at any time."
+"indicates that the user may change their password at any time."
msgstr ""
"Définir le nombre minimum de jours entre chaque changement de mot de passe à "
"<replaceable>MIN_DAYS</replaceable>. Une valeur de zéro pour ce champ "
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned that his/her password is "
+"the password expiring that a user will be warned that their password is "
"about to expire."
msgstr ""
"Configurer le nombre de jours d'avertissement avant que le changement de mot "
#: groupmems.8.xml:86(para)
msgid ""
-"The <command>groupmems</command> command allows a user to administer his/her "
+"The <command>groupmems</command> command allows a user to administer their "
"own group membership list without the requirement of superuser privileges. "
"The <command>groupmems</command> utility is for systems that configure its "
"users to be in their own name sake primary group (i.e., guest / guest)."
msgid ""
"The <command>chage</command> 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 his/her password."
+"is used by the system to determine when a user must change their password."
msgstr ""
"La commande <command>chage</command> modifie le nombre de jours entre les "
"changements de mot de passe et la date du dernier changement. Ces "
msgid ""
"Set the maximum number of days during which a password is valid. When "
"<replaceable>MAX_DAYS</replaceable> plus <replaceable>LAST_DAY</replaceable> "
-"is less than the current day, the user will be required to change his/her "
-"password before being able to use his/her account. This occurrence can be "
+"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>-W</option> option, which "
"provides the user with advance warning."
msgstr ""
msgid ""
"Set the number of days of warning before a password change is required. The "
"<replaceable>WARN_DAYS</replaceable> option is the number of days prior to "
-"the password expiring that a user will be warned his/her password is about "
+"the password expiring that a user will be warned their password is about "
"to expire."
msgstr ""
"Configurer le nombre de jours d'avertissement avant que le changement de mot "
msgid ""
"The <command>chage</command> command is restricted to the root user, except "
"for the <option>-l</option> option, which may be used by an unprivileged "
-"user to determine when his/her password or account is due to expire."
+"user to determine when their password or account is due to expire."
msgstr ""
"La commande <command>chage</command> est réservée à l'utilisateur root, sauf "
"pour l'option <option>-l</option>, qui peut être utilisée par un utilisateur "
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~| "GROUPS\n"
#~| " mentioned by the -G option without "
#~| "removing\n"
-#~| " him/her from other groups\n"
+#~| " the user from other groups\n"
#~| " -h, --help display this help message and exit\n"
#~| " -l, --login NEW_LOGIN new value of the login name\n"
#~| " -L, --lock lock the user account\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append ユーザを (-G で指定された) 補助グループ群\n"
" GROUPS に追加する。他のグループからの削除は\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append пайдаланушыны қосымша ТОПТАР ішіне қосу\n"
" -G опциясы сияқты, пайдаланушыны басқа "
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~| "GROUPS\n"
#~| " mentioned by the -G option without "
#~| "removing\n"
-#~| " him/her from other groups\n"
+#~| " the user from other groups\n"
#~| " -h, --help display this help message and exit\n"
#~| " -l, --login NEW_LOGIN new value of the login name\n"
#~| " -L, --lock lock the user account\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append legg til brukeren i de ekstra gruppene "
"listet i \n"
#~| "GROUPS\n"
#~| " mentioned by the -G option without "
#~| "removing\n"
-#~| " him/her from other groups\n"
+#~| " the user from other groups\n"
#~| " -h, --help display this help message and exit\n"
#~| " -l, --login NEW_LOGIN new value of the login name\n"
#~| " -L, --lock lock the user account\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append voeg de gebruiker toe aan de bijkomende "
"GROEPEN,\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append juntar o utilizador aos GRUPOS\n"
" suplementares mencionados pela opção -G\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append anexa o usuário para os GRUPOS "
"suplementares\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append добавить пользователя в дополнительные\n"
" ГРУППЫ, указанные в параметре -G не удаляя\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~| "GROUPS\n"
#~| " mentioned by the -G option without "
#~| "removing\n"
-#~| " him/her from other groups\n"
+#~| " the user from other groups\n"
#~| " -h, --help display this help message and exit\n"
#~| " -l, --login NEW_LOGIN new value of the login name\n"
#~| " -L, --lock lock the user account\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append lägg till användaren till ytterligare "
"GRUPPER\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~| "GROUPS\n"
#~| " mentioned by the -G option without "
#~| "removing\n"
-#~| " him/her from other groups\n"
+#~| " the user from other groups\n"
#~| " -h, --help display this help message and exit\n"
#~| " -l, --login NEW_LOGIN new value of the login name\n"
#~| " -L, --lock lock the user account\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append thêm người dùng vào các nhóm phụ\n"
" đưa ra bởi tùy chọn “-G” mà không gỡ bỏ ta "
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
" -a, --append GROUP 将用户追加至上边 -G 中提到的附加组中，\n"
" 并不从其它组中删除此用户\n"
#~ "GROUPS\n"
#~ " mentioned by the -G option without "
#~ "removing\n"
-#~ " him/her from other groups\n"
+#~ " the user from other groups\n"
#~ " -h, --help display this help message and exit\n"
#~ " -l, --login NEW_LOGIN new value of the login name\n"
#~ " -L, --lock lock the user account\n"
msgid ""
" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
-" him/her from other groups\n"
+" the user from other groups\n"
msgstr ""
msgid " -l, --login NEW_LOGIN new value of the login name\n"
(void) fputs (_(" -G, --groups GROUPS new list of supplementary GROUPS\n"), usageout);
(void) fputs (_(" -a, --append append the user to the supplemental GROUPS\n"
" mentioned by the -G option without removing\n"
- " him/her from other groups\n"), usageout);
+ " the user from other groups\n"), usageout);
(void) fputs (_(" -h, --help display this help message and exit\n"), usageout);
(void) fputs (_(" -l, --login NEW_LOGIN new value of the login name\n"), usageout);
(void) fputs (_(" -L, --lock lock the user account\n"), usageout);
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
- him/her from other groups
+ the user from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
# mind.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
projects / shadow / commitdiff