DOKK / manpages / debian 11 / libuser / lusermod.1.en
lusermod(1) General Commands Manual lusermod(1)

lusermod - Modify an user

lusermod [OPTION]... user

Modifies the user with name user.

Set user's GECOS field to gecos. The GECOS field is traditionally used to store user's real name and other information.

Set user's home directory to directory.

Change user's primary group ID to gid. If group with ID gid does not exist, a warning is printed, but the operation is performed anyway.

Ask all questions when connecting to the user database, even if default answers are set up in libuser configuration.

Lock user's account. This prevents logging in using user's password.

Rename user to name.

After changing user's home directory (using the -d option), move the old home directory to the new location.

Set user's password to password. Note that the password can be viewed while running lusermod using tools such as ps(1).

Set user's password to the password represented by the hash encrypted. Note that the hash can be viewed while running lusermod using tools such as ps(1).

Set user's login shell to shell.

Unlock user's account.

Change user's user ID to uid.

Set user's common name to name. This attribute is only supported in some backends (e.g.LDAP), and its support may have further limitations (e.g. LDAP schema rules).

Set user's given name to name. This attribute is only supported in some backends (e.g.LDAP), and its support may have further limitations (e.g. LDAP schema rules).

Set user's home telephone number to phone. This attribute is only supported in some backends (e.g.LDAP), and its support may have further limitations (e.g. LDAP schema rules).

Set user's room number to room. This attribute is only supported in some backends (e.g.LDAP), and its support may have further limitations (e.g. LDAP schema rules).

Set user's surname to name. This attribute is only supported in some backends (e.g.LDAP), and its support may have further limitations (e.g. LDAP schema rules).

Set user's telephone number to phone. This attribute is only supported in some backends (e.g.LDAP), and its support may have further limitations (e.g. LDAP schema rules).

The exit status is 0 on success, nonzero on error.

2009-12-11 libuser