table of contents
- Tumbleweed 4.20.0-1.1
- Leap-16.0
- Leap-15.6
| USERADD(8) | System Management Commands | USERADD(8) |
NAME¶
useradd - create a new user or update default new user information
SYNOPSIS¶
useradd [options] LOGIN
useradd -D
useradd -D [options]
DESCRIPTION¶
When invoked without the -D option, the useradd command creates a new user account using the values specified on the command line plus the default values from the system. Depending on command line options, the useradd command will update system files and may also create the new user's home directory and copy initial files.
By default, a group will also be created for the new user (see -g, -N, -U, and USERGROUPS_ENAB).
OPTIONS¶
The options which apply to the useradd command are:
--badname
-b, --base-dir BASE_DIR
If this option is not specified, useradd will use the base directory specified by the HOME variable in /etc/default/useradd, or /home by default.
--btrfs-subvolume-home
If this option is not specified, useradd will follow the default behavior defined by the BTRFS_SUBVOLUME_HOME variable in /etc/default/useradd. If this variable is not set, the default value is no.
When the --btrfs-subvolume-home command-line option is specified, a Btrfs subvolume is created regardless of any configuration file settings.
Subvolumes are only created for regular users, whose UID is within the UID_MIN-UID_MAX range defined in /etc/login.defs. System users get a regular home directory instead. Set the BTRFS_SUBVOLUME_SYSTEM variable in /etc/default/useradd to yes to create subvolumes for system users as well. If this variable is not set, the default value is no.
If the parent directory of the user's home directory is not on a Btrfs filesystem, useradd will not create a subvolume. Instead, it creates a regular directory, prints a warning to standard error, and logs the event via syslog at level LOG_WARN. The user account is still created successfully.
If the filesystem type cannot be determined (e.g., because of insufficient permissions, an I/O error, or a statfs(2) failure), useradd treats this as a fatal error: the home directory is not created, the command exits with a non-zero status (E_HOMEDIR, 12), and an error message is printed.
-c, --comment COMMENT
-d, --home-dir HOME_DIR
-D, --defaults
-e, --expiredate EXPIRE_DATE
If not specified, useradd uses the default expiry date specified by the EXPIRE variable in /etc/default/useradd, or an empty string (no expiry) by default.
-f, --inactive INACTIVE
A value of 0 disables the account when the password expires, with no delay.
A value of -1 empties the respective field in the shadow password file, which means that the inactivity period is not enforced.
If not specified, useradd uses the default inactivity period specified by the INACTIVE variable in /etc/default/useradd, or -1 by default if no value is specified.
-F, --add-subids-for-system
-g, --gid GROUP
If not specified, the behavior of useradd will depend on the USERGROUPS_ENAB variable in /etc/login.defs. If this variable is set to yes (or -U/--user-group is specified on the command line), a group will be created for the user, with the same name as the loginname. If the variable is set to no (or -N/--no-user-group is specified on the command line), useradd will set the primary group of the new user to the value specified by the GROUP variable in /etc/default/useradd, or 1000 by default.
-G, --groups GROUP1[,GROUP2,...[,GROUPN]]]
-h, --help
-k, --skel SKEL_DIR
This option is only valid if the -m (or --create-home) option is specified.
If this option is not set, the skeleton directory is defined by the SKEL variable in /etc/default/useradd or, by default, /etc/skel.
Absolute symlinks that link back to the skel directory will have the /etc/skel prefix replaced with the user's home directory.
If possible, the ACLs and extended attributes are copied.
-K, --key KEY=VALUE
Example: -K PASS_MAX_DAYS =-1 can be used when creating an account to turn off password aging. Multiple -K options can be specified, e.g.: -K UID_MIN =100 -K UID_MAX=499
-l, --no-log-init
By default, the user's entries in the lastlog and faillog databases are reset to avoid reusing the entry from a previously deleted user.
If this option is not specified, useradd will also consult the variable LOG_INIT in the /etc/default/useradd if set to no the user will not be added to the lastlog and faillog databases.
-m, --create-home
By default, if this option is not specified and CREATE_HOME is not enabled, no home directories are created.
The directory where the user's home directory is created must exist and have proper SELinux context and permissions. Otherwise the user's home directory cannot be created or accessed.
-M, --no-create-home
-N, --no-user-group
The default behavior (if the -g, -N, and -U options are not specified) is defined by the USERGROUPS_ENAB variable in /etc/login.defs.
-o, --non-unique
This option is only valid in combination with the -u option. As a user identity serves as key to map between users on one hand and permissions, file ownerships and other aspects that determine the system's behavior on the other hand, more than one login name will access the account of the given UID.
-p, --password PASSWORD
Without this option, the new account will be locked and with no password defined, i.e. a single exclamation mark in the respective field of /etc/shadow. This is a state where the user won't be able to access the account or to define a password himself.
Note:Avoid this option on the command line because the password (or encrypted password) will be visible by users listing the processes.
You should make sure the password respects the system's password policy.
-r, --system
System users will be created with no aging information in /etc/shadow, and their numeric identifiers are chosen in the SYS_UID_MIN-SYS_UID_MAX range, defined in /etc/login.defs, instead of UID_MIN-UID_MAX (and their GID counterparts for the creation of groups).
Note that useradd will not create a home directory for such a user, regardless of the default setting in /etc/login.defs (CREATE_HOME). You have to specify the -m options if you want a home directory for a system account to be created.
Note that this option will not update /etc/subuid and /etc/subgid. You have to specify the -F options if you want to update the files for a system account to be created.
-R, --root CHROOT_DIR
-P, --prefix PREFIX_DIR
-s, --shell SHELL
-u, --uid UID
See also the -r option and the UID_MAX description.
-U, --user-group
The default behavior (if the -g, -N, and -U options are not specified) is defined by the USERGROUPS_ENAB variable in /etc/login.defs.
-Z, --selinux-user SEUSER
--selinux-range SERANGE
This option is only valid if the -Z (or --selinux-user) option is specified.
Changing the default values¶
When invoked with only the -D option, useradd will display the current default values. When invoked with -D plus other options, useradd will update the default values for the specified options. Valid default-changing options are:
-b, --base-dir BASE_DIR
This option sets the HOME variable in /etc/default/useradd.
-e, --expiredate EXPIRE_DATE
This option sets the EXPIRE variable in /etc/default/useradd.
-f, --inactive INACTIVE
This option sets the INACTIVE variable in /etc/default/useradd.
-g, --gid GROUP
This option sets the GROUP variable in /etc/default/useradd.
-s, --shell SHELL
This option sets the SHELL variable in /etc/default/useradd.
NOTES¶
The system administrator is responsible for placing the default user files in the /etc/skel/ directory (or any other skeleton directory specified in /etc/default/useradd or on the command line).
CAVEATS¶
You may not add a user to a NIS or LDAP group. This must be performed on the corresponding server.
Similarly, if the username already exists in an external user database such as NIS or LDAP, useradd will deny the user account creation request.
Usernames may contain only lower and upper case letters, digits, underscores, dashes, or dots. They can end with a dollar sign. Dashes are not allowed at the beginning of the username. Fully numeric usernames and usernames . or .. are also disallowed. It is not recommended to use usernames beginning with . character as their home directories will be hidden in the ls output.
Usernames may only be up to 256 characters long.
CONFIGURATION¶
The following configuration variables in /etc/login.defs change the behavior of this tool:
CREATE_HOME (boolean)
This setting does not apply to system users, and can be overridden on the command line.
GID_MAX (number), GID_MIN (number)
The default value for GID_MIN (resp. GID_MAX) is 1000 (resp. 60000).
HOME_MODE (number)
useradd and newusers use this to set the mode of the home directory they create.
LASTLOG_UID_MAX (number)
No LASTLOG_UID_MAX option present in the configuration means that there is no user ID limit for writing lastlog entries.
MAIL_DIR (string)
MAIL_FILE (string)
The MAIL_DIR and MAIL_FILE variables are used by useradd, usermod, and userdel to create, move, or delete the user's mail spool.
If MAIL_CHECK_ENAB is set to yes, they are also used to define the MAIL environment variable.
MAX_MEMBERS_PER_GROUP (number)
The default value is 0, meaning that there are no limits in the number of members in a group.
This feature (split group) permits to limit the length of lines in the group file. This is useful to make sure that lines for NIS groups are not larger than 1024 characters.
If you need to enforce such limit, you can use 25.
Note: split groups may not be supported by all tools (even in the Shadow toolsuite). You should not use this variable unless you really need it.
PASS_MAX_DAYS (number)
PASS_WARN_AGE (number)
SUB_GID_MIN (number), SUB_GID_MAX (number), SUB_GID_COUNT (number)
The default values for SUB_GID_MIN, SUB_GID_MAX, SUB_GID_COUNT are respectively 100000, 600100000 and 65536.
SUB_GID_DETERMINISTIC (boolean)
start = SUB_GID_MIN + ((UID - UID_MIN) * SUB_GID_COUNT)
end = start + SUB_GID_COUNT - 1
This ensures the same UID always receives the same subordinate GID range on every system, making it suitable for environments with centralized user management (LDAP, NIS, etc.) or synchronized UIDs across systems.
If SUB_GID_DETERMINISTIC is enabled, you can use usermod --add-subgids -S to produce deterministic subgids.
WARNING: Because UID_MIN is used to calculate the ranges, any change of UID_MIN will change the ranges calculated. SUB_GID_COUNT is used to calculate the ranges, any change of SUB_GID_COUNT will change the ranges calculated. Users with identities less than UID_MIN are incompatible with SUB_GID_DETERMINISTIC, but can still be set manually.
WARNING: Do not mix deterministic and linear (default) allocation on the same system or across systems sharing /etc/subgid via network storage (NFS, etc.). Mixing allocation methods will cause subordinate ID range conflicts and overlaps .
The default value for SUB_GID_DETERMINISTIC is no.
Range Calculation Examples¶
With default configuration (UID_MIN=1000, SUB_GID_MIN=100000, SUB_GID_COUNT=65536):
| UID | Calculation | Subordinate GID Range |
| 1000 | 100000 + ((1000-1000) * 65536) | 100000-165535 |
| 1001 | 100000 + ((1001-1000) * 65536) | 165536-231071 |
| 1002 | 100000 + ((1002-1000) * 65536) | 231072-296607 |
| 1100 | 100000 + ((1100-1000) * 65536) | 6653600-6719135 |
Subordinate ID Space Planning¶
When planning subordinate ID allocation, calculate the maximum number of users the space can accommodate:
capacity = (SUB_GID_MAX - SUB_GID_MIN) / SUB_GID_COUNT
With default values: (600100000 - 100000) / 65536 ≈ 9155 users.
For high-density environments with many users and smaller allocations:
SUB_GID_COUNT 4096
SUB_GID_MIN 100000
SUB_GID_MAX 10000000
This gives: (10000000 - 100000) / 4096 ≈ 2417 users.
UNSAFE_SUB_GID_DETERMINISTIC_WRAP (boolean)
Only effective when SUB_GID_DETERMINISTIC is set to yes.
When set to yes (WRAP MODE), allows the deterministic range calculation to wrap around using modulo arithmetic when a UID would overflow the configured subordinate ID space. The subordinate ID space is treated as a ring buffer.
WARNING: Range overlaps can lead to container escapes and privilege escalation. For example, with SUB_GID_MIN=100000, SUB_GID_MAX=200000, SUB_GID_COUNT=65536, User A (UID 1000) gets range [100000, 165535] and User B (UID 1001) wraps and overlaps with User A. User B's container can now access files from User A's containers.
Use only in development, testing, or tightly constrained lab environments.
When set to no (default), any arithmetic overflow or range exceeding SUB_GID_MAX is a hard error. This guarantees non-overlapping, monotonic allocation.
The default value for UNSAFE_SUB_GID_DETERMINISTIC_WRAP is no.
SUB_UID_MIN (number), SUB_UID_MAX (number), SUB_UID_COUNT (number)
The default values for SUB_UID_MIN, SUB_UID_MAX, SUB_UID_COUNT are respectively 100000, 600100000 and 65536.
SUB_UID_DETERMINISTIC (boolean)
start = SUB_UID_MIN + ((UID - UID_MIN) * SUB_UID_COUNT)
end = start + SUB_UID_COUNT - 1
This ensures the same UID always receives the same subordinate UID range on every system, making it suitable for environments with centralized user management (LDAP, NIS, etc.) or synchronized UIDs across systems.
If SUB_UID_DETERMINISTIC is enabled, you can use usermod --add-subuids -S to produce deterministic subuids.
WARNING: Because UID_MIN is used to calculate the ranges, any change of UID_MIN will change the ranges calculated. SUB_UID_COUNT is used to calculate the ranges, any change of SUB_UID_COUNT will change the ranges calculated. Users with identities less than UID_MIN are incompatible with SUB_UID_DETERMINISTIC, but can still be set manually.
WARNING: Do not mix deterministic and linear (default) allocation on the same system or across systems sharing /etc/subuid via network storage (NFS, etc.). Mixing allocation methods will cause subordinate ID range conflicts and overlaps .
The default value for SUB_UID_DETERMINISTIC is no.
Range Calculation Examples¶
With default configuration (UID_MIN=1000, SUB_UID_MIN=100000, SUB_UID_COUNT=65536):
| UID | Calculation | Subordinate UID Range |
| 1000 | 100000 + ((1000-1000) * 65536) | 100000-165535 |
| 1001 | 100000 + ((1001-1000) * 65536) | 165536-231071 |
| 1002 | 100000 + ((1002-1000) * 65536) | 231072-296607 |
| 1100 | 100000 + ((1100-1000) * 65536) | 6653600-6719135 |
Subordinate ID Space Planning¶
When planning subordinate ID allocation, calculate the maximum number of users the space can accommodate:
capacity = (SUB_UID_MAX - SUB_UID_MIN) / SUB_UID_COUNT
With default values: (600100000 - 100000) / 65536 ≈ 9155 users.
For high-density environments with many users and smaller allocations:
SUB_UID_COUNT 4096
SUB_UID_MIN 100000
SUB_UID_MAX 10000000
This gives: (10000000 - 100000) / 4096 ≈ 2417 users.
UNSAFE_SUB_UID_DETERMINISTIC_WRAP (boolean)
Only effective when SUB_UID_DETERMINISTIC is set to yes.
When set to yes (WRAP MODE), allows the deterministic range calculation to wrap around using modulo arithmetic when a UID would overflow the configured subordinate ID space. The subordinate ID space is treated as a ring buffer.
WARNING: Range overlaps can lead to container escapes and privilege escalation. For example, with SUB_UID_MIN=100000, SUB_UID_MAX=200000, SUB_UID_COUNT=65536, User A (UID 1000) gets range [100000, 165535] and User B (UID 1001) wraps and overlaps with User A. User B's container can now access files from User A's containers.
Use only in development, testing, or tightly constrained lab environments.
When set to no (default), any arithmetic overflow or range exceeding SUB_UID_MAX is a hard error. This guarantees non-overlapping, monotonic allocation.
The default value for UNSAFE_SUB_UID_DETERMINISTIC_WRAP is no.
SYS_GID_MAX (number), SYS_GID_MIN (number)
The default value for SYS_GID_MIN (resp. SYS_GID_MAX) is 101 (resp. GID_MIN-1).
SYS_UID_MAX (number), SYS_UID_MIN (number)
The default value for SYS_UID_MIN (resp. SYS_UID_MAX) is 101 (resp. UID_MIN-1).
UID_MAX (number), UID_MIN (number)
The default value for UID_MIN (resp. UID_MAX) is 1000 (resp. 60000).
UMASK (number)
useradd and newusers use this mask to set the mode of the home directory they create if HOME_MODE is not set.
It is also used by login to define users' initial umask. Note that this mask can be overridden by the user's GECOS line (if QUOTAS_ENAB is set) or by the specification of a limit with the K identifier in limits(5).
USERGROUPS_ENAB (boolean)
If set to yes, userdel will remove the user's group if it contains no more members, and useradd will create by default a group with the name of the user.
FILES¶
/etc/passwd
/etc/shadow
/etc/group
/etc/gshadow
/etc/default/useradd
/etc/shadow-maint/useradd-pre.d/*, /etc/shadow-maint/useradd-post.d/*
/etc/skel/
/etc/subgid
/etc/subuid
/etc/login.defs
EXIT VALUES¶
The useradd command exits with the following values:
0
1
2
3
4
6
9
10
12
14
19
SEE ALSO¶
chfn(1), chsh(1), passwd(1), crypt(3), groupadd(8), groupdel(8), groupmod(8), login.defs(5), newusers(8), subgid(5), subuid(5), userdel(8), usermod(8).
| 07/29/2026 | shadow-utils 4.20.0 |