{ "mode": "man", "parameter": "adduser", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/adduser/8/json", "generated": "2026-09-23T16:55:08Z", "synopsis": "adduser [--add-extra-groups] [--allow-all-names] [--allow-bad-names] [--comment comment]\n[--conf file] [--debug] [--disabled-login] [--disabled-password] [--encrypt-home]\n[--firstgid id] [--firstuid id] [--gid id] [--home dir] [--ingroup group]\n[--lastgid id] [--lastuid id] [--no-create-home] [--shell shell] [--quiet] [--uid id]\n[--verbose] [--stdoutmsglevel prio] [--stderrmsglevel prio] [--logmsglevel prio] user\nadduser --system [--comment comment] [--conf file] [--debug] [--gid id] [--group]\n[--home dir] [--ingroup group] [--no-create-home] [--shell shell] [--uid id]\n[--quiet] [--verbose] [--stdoutmsglevel prio] [--stderrmsglevel prio]\n[--logmsglevel prio] user\nadduser --group [--conf file] [--debug] [--firstgid id] [--gid ID] [--lastgid id] [--quiet]\n[--verbose] [--stdoutmsglevel prio] [--stderrmsglevel prio] [--logmsglevel prio]\ngroup\naddgroup [--conf file] [--debug] [--firstgid id] [--gid ID] [--lastgid id] [--quiet]\n[--verbose] [--stdoutmsglevel prio] [--stderrmsglevel prio] [--logmsglevel prio]\ngroup\naddgroup --system [--gid id] [--conf file] [--quiet] [--verbose] [--stdoutmsglevel prio]\n[--stderrmsglevel prio] [--logmsglevel prio] group\nadduser [--conf file] [--debug] [--quiet] [--verbose] [--stdoutmsglevel prio]\n[--stderrmsglevel prio] [--logmsglevel prio] user group", "sections": { "NAME": { "content": "adduser, addgroup - add or manipulate users or groups\n", "subsections": [] }, "SYNOPSIS": { "content": "adduser [--add-extra-groups] [--allow-all-names] [--allow-bad-names] [--comment comment]\n[--conf file] [--debug] [--disabled-login] [--disabled-password] [--encrypt-home]\n[--firstgid id] [--firstuid id] [--gid id] [--home dir] [--ingroup group]\n[--lastgid id] [--lastuid id] [--no-create-home] [--shell shell] [--quiet] [--uid id]\n[--verbose] [--stdoutmsglevel prio] [--stderrmsglevel prio] [--logmsglevel prio] user\n\nadduser --system [--comment comment] [--conf file] [--debug] [--gid id] [--group]\n[--home dir] [--ingroup group] [--no-create-home] [--shell shell] [--uid id]\n[--quiet] [--verbose] [--stdoutmsglevel prio] [--stderrmsglevel prio]\n[--logmsglevel prio] user\n\nadduser --group [--conf file] [--debug] [--firstgid id] [--gid ID] [--lastgid id] [--quiet]\n[--verbose] [--stdoutmsglevel prio] [--stderrmsglevel prio] [--logmsglevel prio]\ngroup\n\naddgroup [--conf file] [--debug] [--firstgid id] [--gid ID] [--lastgid id] [--quiet]\n[--verbose] [--stdoutmsglevel prio] [--stderrmsglevel prio] [--logmsglevel prio]\ngroup\n\naddgroup --system [--gid id] [--conf file] [--quiet] [--verbose] [--stdoutmsglevel prio]\n[--stderrmsglevel prio] [--logmsglevel prio] group\n\nadduser [--conf file] [--debug] [--quiet] [--verbose] [--stdoutmsglevel prio]\n[--stderrmsglevel prio] [--logmsglevel prio] user group\n", "subsections": [ { "name": "adduser --help", "content": "" }, { "name": "adduser --version", "content": "" } ] }, "DESCRIPTION": { "content": "adduser and addgroup add users and groups to the system according to command line options and\nconfiguration information in /etc/adduser.conf. They are friendlier front ends to the low\nlevel tools like useradd, groupadd and usermod programs, by default choosing Debian policy\nconformant UID and GID values, creating a home directory with skeletal configuration, running\na custom script, and other features.\n\nadduser and addgroup are intended as a policy layer, making it easier for package maintainers\nand local administrators to create local system accounts in the way Debian expects them to be\ncreated, taking the burden to adapt to the probably changing specifications of Debian policy.\nadduser --system takes special attention on just needing a single call in the package main‐\ntainer scripts without any conditional wrappers, error suppression or other scaffolding.\n\nadduser honors the distinction between dynamically allocated system users and groups and dy‐\nnamically allocated user accounts that is documented in Debian Policy, Chapter 9.2.2.\n\nFor a full list and explanations of all options, see the OPTIONS section.\n\nadduser and addgroup can be run in one of five modes:\n", "subsections": [ { "name": "Add a normal user", "content": "If called with one non-option argument and without the --system or --group options, adduser\nwill add a normal user, that means a dynamically allocated user account in the sense of De‐\nbian Policy. This is commonly referred to in adduser as a non-system user.\n\nadduser will choose the first available UID from the range specified by FIRSTUID and\nLASTUID in the configuration file. The range may be overridden with the --firstuid and\n--lastuid options. Finally, the UID can be set fully manually with the --uid option.\n\nBy default, each user is given a corresponding group with the same name. This is commonly\ncalled Usergroups and allows group writable directories to be easily maintained by placing\nthe appropriate users in the new group, setting the set-group-ID bit in the directory, and\nensuring that all users use a umask of 002.\n\nFor a usergroup, adduser will choose the first available GID from the range specified by\nFIRSTGID and LASTGID in the configuration file. The range may be overridden with the\n--firstgid and --lastgid options. Finally, the GID can be set fully manually with the --gid\noption.\n\nThe interaction between USERSGID, USERSGROUP, and USERGROUPS is explained in detail in ad‐\nduser.conf(5).\n\nUsers' primary groups can also be overridden from the command line with the --gid or --in‐\ngroup options to set the group by id or name, respectively. Also, users can be added to one\nor more supplemental groups defined as EXTRAGROUPS in the configuration file either by set‐\nting ADDEXTRAGROUPS to 1 in the configuration file, or by passing --add-extra-groups on the\ncommand line.\n\nadduser will copy files from /etc/skel into the home directory and prompt for the comment\nfield and a password if those functions have not been turned off / overridden from the com‐\nmand line.\n\nUID, comment, home directory and shell might be pre-determined with the UIDPOOL and GIDPOOL\noption, documented in adduser.conf(5).\n\nTo set up an encrypted home directory for the new user, add the --encrypt-home option. For\nmore information, refer to the -b option of ecryptfs-setup-private(1).\n\n" }, { "name": "Add a system user", "content": "If called with one non-option argument and the --system option, adduser will add a dynami‐\ncally allocated system user, often abbreviated as system user in the context of the adduser\npackage.\n\nadduser will choose the first available UID from the range specified by FIRSTSYSTEMUID and\nLASTSYSTEMUID in the configuration file. This can be overridden with the --uid option.\n\nBy default, system users are placed in the nogroup group. To place the new system user in an\nalready existing group, use the --gid or --ingroup options. If the --group is given and the\nidentically named group does not already exist, it is created with the same ID.\n\nIf no home directory is specified, the default home directory for a new system user is\n/nonexistent. This directory should never exist on any Debian system, and adduser will never\ncreate it automatically.\n\nUnless a shell is explicitly set with the --shell option, the new system user will have the\nshell set to /usr/sbin/nologin. adduser --system does not set a password for the new ac‐\ncount. Skeletal configuration files are not copied.\n\nOther options will behave as for the creation of a normal user. The files referenced by\nUIDPOOL and GIDPOOL do also work.\n\n" }, { "name": "Add a group", "content": "If adduser is called with the --group option and without the --system option, or addgroup is\ncalled respectively, a user group will be added.\n\nA dynamically allocated system group, often abbreviated as system group in the context of the\nadduser package, will be created if adduser is called with the --system option.\n\nA GID will be chosen from the respective range specified for GIDs in the configuration file\n(FIRSTGID, LASTGID, FIRSTSYSTEMGID, LASTSYSTEMGID). To override that mechanism, you\ncan give the GID using the --gid option.\n\nFor non-system groups, the range specified in the configuration file may be overridden with\nthe --firstgid and --lastgid options.\n\nThe group is created with no members.\n\n" }, { "name": "Add an existing user to an existing group", "content": "If called with two non-option arguments, adduser will add an existing user to an existing\ngroup.\n\n" } ] }, "OPTIONS": { "content": "Different modes of adduser allow different options. If no valid modes are listed for a op‐\ntion, it is accepted in all modes.\n\nShort versions for certain options may exist for historical reasons. They are going to stay\nsupported, but are removed from the documentation. Users are advised to migrate to the long\nversion of options.\n", "subsections": [ { "name": "--add-extra-groups", "content": "Add new user to extra groups defined in the configuration files' EXTRAGROUPS setting.\nThe old spelling --addextragroups is deprecated and will be supported in Debian\nbookworm only. Valid Modes: adduser, adduser --system.\n", "long": "--add-extra-groups" }, { "name": "--allow-all-names", "content": "Allow any user- and groupname which is supported by the underlying useradd(8), includ‐\ning names containing non-ASCII characters. See VALID NAMES in adduser.conf(5). Valid\nModes: adduser, adduser --system, addgroup, addgroup --system.\n", "long": "--allow-all-names" }, { "name": "--allow-bad-names", "content": "Disable NAMEREGEX and SYSNAMEREGEX check of names. Only a weaker check for valid‐\nity of the name is applied. See VALID NAMES in adduser.conf(5). Valid Modes: ad‐\nduser, adduser --system, addgroup, addgroup --system.\n\n--comment comment\nSet the comment field for the new entry generated. adduser will not ask for the in‐\nformation if this option is given. This field is also known under the name GECOS\nfield and contains information that is used by the finger(1) command. This used to be\nthe --gecos option, which is deprecated and will be removed after Debian bookworm.\nValid Modes: adduser, adduser --system.\n\n--conf file\nUse file instead of /etc/adduser.conf. Multiple --conf options can be given.\n", "long": "--allow-bad-names" }, { "name": "--debug", "content": "Synonymous to --stdoutmsglevel=debug. Deprecated.\n", "long": "--debug" }, { "name": "--disabled-login", "content": "", "long": "--disabled-login" }, { "name": "--disabled-password", "content": "Do not run passwd(1) to set a password. In most situations, logins are still possible\nthough (for example using SSH keys or through PAM) for reasons that are beyond ad‐\nduser's scope. --disabled-login will additionally set the shell to /usr/sbin/nologin.\nValid Mode: adduser.\n\n--firstuid ID\n--lastuid ID\n--firstgid ID\n--lastgid ID\nOverride the first UID / last UID / first GID / last GID in the range that the uid is\nchosen from (FIRSTUID, LASTUID, FIRSTGID and LASTGID, FIRSTSYSTEMUID, LASTSYS‐\nTEMUID, FIRSTSYSTEMGID and LASTSYSTEMGID in the configuration file). If a group\nis created as a usergroup, --firstgid and --lastgid are ignored. The group gets the\nsame ID as the user. Valid Modes: adduser, adduser --system, for --firstgid and\n--lastgid also addgroup.\n", "long": "--disabled-password" }, { "name": "--force-badname", "content": "", "long": "--force-badname" }, { "name": "--allow-badname", "content": "These are the deprecated forms of --allow-bad-names. It will be removed during the\nrelease cycle of the Debian release after bookworm.\n", "long": "--allow-badname" }, { "name": "--extrausers", "content": "Uses extra users as the database.\n\n--gid ID\nWhen creating a group, this option sets the group ID number of the new group to GID.\nWhen creating a user, this option sets the primary group ID number of the new user to\nGID. Valid Modes: adduser, adduser --system, addgroup, addgroup --system.\n", "long": "--extrausers" }, { "name": "--group", "content": "Using this option in adduser --system indicates that the new user should get an iden‐\ntically named group as its primary group. If that identically named group is not al‐\nready present, it is created. If not combined with --system, a group with the given\nname is created. The latter is the default action if the program is invoked as ad‐\ndgroup. Valid Modes: adduser --system, addgroup, addgroup --system.\n\n--help Display brief instructions.\n\n--home dir\nUse dir as the user's home directory, rather than the default specified by the config‐\nuration file (or /nonexistent if adduser --system is used). If the directory does not\nexist, it is created. Valid Modes: adduser, adduser --system.\n\n--ingroup GROUP\nWhen creating a user, this option sets the primary group ID number of the new user to\nthe GID of the named group. Unlike with the --gid option, the group is specified here\nby name rather than by numeric ID number. The group must already exist. Valid Modes:\nadduser, adduser --system.\n\n--lastuid ID\n--lastgid ID\nOverride the last UID / last GID. See --firstuid.\n", "long": "--group" }, { "name": "--no-create-home", "content": "Do not create a home directory for the new user. Note that the pathname for the new\nuser's home directory will still be entered in the appropriate field in the\n/etc/passwd file. The use of this option does not imply that this field should be\nempty. Rather, it indicates to adduser that some other mechanism will be responsible\nfor initializing the new user's home directory. Valid Modes: adduser, adduser --sys‐\ntem.\n", "long": "--no-create-home" }, { "name": "--quiet", "content": "Synonymous to --stdoutmsglevel=warn. Deprecated.\n\n--shell shell\nUse shell as the user's login shell, rather than the default specified by the configu‐\nration file (or /usr/sbin/nologin if adduser --system is used). Valid Modes: adduser,\nadduser --system.\n", "long": "--quiet" }, { "name": "--system", "content": "Nomally, adduser creates dynamically allocated user accounts and groups as defined in\nDebian Policy, Chapter 9.2.2. With this option, adduser creates a dynamically allo‐\ncated system user and group and changes its mode respectively. Valid Modes: adduser,\naddgroup.\n\n--uid ID\nForce the new userid to be the given number. adduser will fail if the userid is al‐\nready taken. Valid Modes: adduser, adduser --system.\n", "long": "--system" }, { "name": "--verbose", "content": "Synonymous to --stdoutmsglevel=info. Deprecated.\n\n--stdoutmsglevel prio\n--stderrmsglevel prio\n--logmsglevel prio\nMinimum priority for messages logged to syslog/journal and the console, respectively.\nValues are trace, debug, info, warn, err, and fatal. Messages with the priority set\nhere or higher get printed to the respective medium. Messages printed to stderr are\nnot repeated on stdout. That allows the local admin to control adduser's chattiness\non the console and in the log independently, keeping probably confusing information to\nitself while still leaving helpful information in the log.\n", "long": "--verbose" }, { "name": "-v --version", "content": "Display version and copyright information.\n\n", "flag": "-v", "long": "--version" } ] }, "EXIT VALUES": { "content": "0 Success: The user or group exists as specified. This can have 2 causes: The user or\ngroup was created by this call to adduser or the user or group was already present on\nthe system as specified before adduser was invoked. If adduser --system is invoked\nfor a user already existing with the requested or compatible attributes, it will also\nreturn 0.\n\n11 The object that adduser was asked to create does already exist.\n\n12 The object that adduser or deluser was asked to operate on does not exist.\n\n13 The object that adduser or deluser was asked to operate on does ont have the proper‐\nties that are required to complete the operation: A user (a group) that was requested\nto be created as a system user (group) does already exist and is not a system user\n(group), or A user (group) that was requested to be created with a certain UID (GID)\ndoes already exist and has a different UID (GID), or A system user (group) that was\nrequested to be deleted does exist, but is not a system user (group).\n\n21 The UID (GID) that was explicitly requested for a new user (group) is already in use.\n\n22 There is no available UID (GID) in the requested range.\n\n23 There is no group with the requested GID for the primary group for a new user.\n\n31 The chosen name for a new user or a new group does not conform to the selected naming\nrules.\n\n32 The home directory of a new user must be an absolute path.\n\n41 The group that was requested to be deleted is not empty.\n\n42 The user that was requested to be removed from a group is not a member in the first\nplace.\n\n43 It is not possible to remove a user from its primary group, or no primary group se‐\nlected for a new user by any method.\n\n51 Incorrect number or order of command line parameters detected.\n\n52 Incompatible options set in configuration file.\n\n53 Mutually incompatible command line options detected.\n\n54 adduser and deluser invoked as non-root and thus cannot work.\n\n55 deluser will refuse to delete the root account.\n\n56 A function was requested that needs more packages to be installed. See Recommends:\nand Suggests: of the adduser package.\n\n61 Adduser was aborted for some reason and tried to roll back the changes that were done\nduring execution.\n\n62 Internal adduser error. This should not happen. Please try to reproduce the issue\nand file a bug report.\n\n71 Error creating and handling the lock.\n\n72 Error accessing the configuration file(s).\n\n73 Error accessing a pool file.\n\n74 Error reading a pool file, syntax error in file.\n\n75 Error accessing auxiliary files.\n\n81 An executable that is needed by adduser or deluser cannot be found. Check your instal‐\nlation and dependencies.\n\n82 Executing an external command returned some unexpected error.\n\n83 An external command was terminated with a signal.\n\n84 A syscall terminated with unexpected error.\n\nOr for many other yet undocumented reasons which are printed to console then. You may then\nconsider to remove --quiet to make adduser more verbose.\n\n", "subsections": [] }, "SECURITY": { "content": "adduser needs root privileges and offers, via the --conf command line option to use different\nconfiguration files. Do not use sudo(8) or similar tools to give partial privileges to ad‐\nduser with restricted command line parameters. This is easy to circumvent and might allow\nusers to create arbitrary accounts. If you want this, consider writing your own wrapper\nscript and giving privileges to execute that script.\n\n", "subsections": [] }, "FILES": { "content": "/etc/adduser.conf\nDefault configuration file for adduser(8) and addgroup(8)\n\n/usr/local/sbin/adduser.local\nOptional custom add-ons, see adduser.local(8)\n\n", "subsections": [] }, "NOTES": { "content": "Unfortunately, the term system account suffers from double use in Debian. It both means an\naccount for the actual Debian system, distinguishing itself from an application account which\nmight exist in the user database of some application running on Debian. A system account in\nthis definition has the potential to log in to the actual system, has a UID, can be member in\nsystem groups, can own files and processes. Debian Policy, au contraire, in its Chapter\n9.2.2, makes a distinguishment of dynamically allocated system users and groups and dynami‐\ncally allocated user accounts, meaning in both cases special instances of system accounts.\nCare must be taken to not confuse this terminology. Since adduser and deluser(8) never ad‐\ndress application accounts and everything in this package concerns system accounts here, the\nusage of the terms user account and system account is actually not ambiguous in the context\nof this package. For clarity, this document uses the definition local system account or\ngroup if the distinction to application accounts or accounts managed in a directory service\nis needed.\n\nadduser used to have the vision to be the universal front end to the various directory ser‐\nvices for creation and deletion of regular and system accounts in Debian since the 1990ies.\nThis vision has been abandoned as of 2022. The rationale behind this includes: that in prac‐\ntice, a small server system is not going to have write access to an enterprise-wide directory\nservice anyway, that locally installed packages are hard to manage with centrally controlled\nsystem accounts, that enterprise directory services have their own management processes any‐\nway and that the personpower of the adduser team is unlikely to be ever strong enough to\nwrite and maintain support for the plethora of directory services that need support.\n\nadduser will constrict itself to being a policy layer for the management of local system ac‐\ncounts, using the tools from the password package for the actual work.\n\n", "subsections": [] }, "BUGS": { "content": "Inconsistent use of terminology around the term system account in docs and code is a bug.\nPlease report this and allow us to improve our docs.\n\nadduser takes special attention to be directly usable in Debian maintainer scripts without\nconditional wrappers, error suppression and other scaffolding. The only thing that the pack‐\nage maintainer should need to code is a check for the presence of the executable in the\npostrm script. The adduser maintainers consider the need for additional scaffolding a bug\nand encourage their fellow Debian package maintainers to file bugs against the adduser pack‐\nage in this case.\n\n", "subsections": [] }, "SEE ALSO": { "content": "adduser.conf(5), deluser(8), groupadd(8), useradd(8), usermod(8), Debian Policy 9.2.2.\n\nDebian GNU/Linux ADDUSER(8)", "subsections": [] } }, "summary": "adduser, addgroup - add or manipulate users or groups", "flags": [ { "flag": "", "long": "--add-extra-groups", "arg": null, "description": "Add new user to extra groups defined in the configuration files' EXTRAGROUPS setting. The old spelling --addextragroups is deprecated and will be supported in Debian bookworm only. Valid Modes: adduser, adduser --system." }, { "flag": "", "long": "--allow-all-names", "arg": null, "description": "Allow any user- and groupname which is supported by the underlying useradd(8), includ‐ ing names containing non-ASCII characters. See VALID NAMES in adduser.conf(5). Valid Modes: adduser, adduser --system, addgroup, addgroup --system." }, { "flag": "", "long": "--allow-bad-names", "arg": null, "description": "Disable NAMEREGEX and SYSNAMEREGEX check of names. Only a weaker check for valid‐ ity of the name is applied. See VALID NAMES in adduser.conf(5). Valid Modes: ad‐ duser, adduser --system, addgroup, addgroup --system. --comment comment Set the comment field for the new entry generated. adduser will not ask for the in‐ formation if this option is given. This field is also known under the name GECOS field and contains information that is used by the finger(1) command. This used to be the --gecos option, which is deprecated and will be removed after Debian bookworm. Valid Modes: adduser, adduser --system. --conf file Use file instead of /etc/adduser.conf. Multiple --conf options can be given." }, { "flag": "", "long": "--debug", "arg": null, "description": "Synonymous to --stdoutmsglevel=debug. Deprecated." }, { "flag": "", "long": "--disabled-login", "arg": null, "description": "" }, { "flag": "", "long": "--disabled-password", "arg": null, "description": "Do not run passwd(1) to set a password. In most situations, logins are still possible though (for example using SSH keys or through PAM) for reasons that are beyond ad‐ duser's scope. --disabled-login will additionally set the shell to /usr/sbin/nologin. Valid Mode: adduser. --firstuid ID --lastuid ID --firstgid ID --lastgid ID Override the first UID / last UID / first GID / last GID in the range that the uid is chosen from (FIRSTUID, LASTUID, FIRSTGID and LASTGID, FIRSTSYSTEMUID, LASTSYS‐ TEMUID, FIRSTSYSTEMGID and LASTSYSTEMGID in the configuration file). If a group is created as a usergroup, --firstgid and --lastgid are ignored. The group gets the same ID as the user. Valid Modes: adduser, adduser --system, for --firstgid and --lastgid also addgroup." }, { "flag": "", "long": "--force-badname", "arg": null, "description": "" }, { "flag": "", "long": "--allow-badname", "arg": null, "description": "These are the deprecated forms of --allow-bad-names. It will be removed during the release cycle of the Debian release after bookworm." }, { "flag": "", "long": "--extrausers", "arg": null, "description": "Uses extra users as the database. --gid ID When creating a group, this option sets the group ID number of the new group to GID. When creating a user, this option sets the primary group ID number of the new user to GID. Valid Modes: adduser, adduser --system, addgroup, addgroup --system." }, { "flag": "", "long": "--group", "arg": null, "description": "Using this option in adduser --system indicates that the new user should get an iden‐ tically named group as its primary group. If that identically named group is not al‐ ready present, it is created. If not combined with --system, a group with the given name is created. The latter is the default action if the program is invoked as ad‐ dgroup. Valid Modes: adduser --system, addgroup, addgroup --system. --help Display brief instructions. --home dir Use dir as the user's home directory, rather than the default specified by the config‐ uration file (or /nonexistent if adduser --system is used). If the directory does not exist, it is created. Valid Modes: adduser, adduser --system. --ingroup GROUP When creating a user, this option sets the primary group ID number of the new user to the GID of the named group. Unlike with the --gid option, the group is specified here by name rather than by numeric ID number. The group must already exist. Valid Modes: adduser, adduser --system. --lastuid ID --lastgid ID Override the last UID / last GID. See --firstuid." }, { "flag": "", "long": "--no-create-home", "arg": null, "description": "Do not create a home directory for the new user. Note that the pathname for the new user's home directory will still be entered in the appropriate field in the /etc/passwd file. The use of this option does not imply that this field should be empty. Rather, it indicates to adduser that some other mechanism will be responsible for initializing the new user's home directory. Valid Modes: adduser, adduser --sys‐ tem." }, { "flag": "", "long": "--quiet", "arg": null, "description": "Synonymous to --stdoutmsglevel=warn. Deprecated. --shell shell Use shell as the user's login shell, rather than the default specified by the configu‐ ration file (or /usr/sbin/nologin if adduser --system is used). Valid Modes: adduser, adduser --system." }, { "flag": "", "long": "--system", "arg": null, "description": "Nomally, adduser creates dynamically allocated user accounts and groups as defined in Debian Policy, Chapter 9.2.2. With this option, adduser creates a dynamically allo‐ cated system user and group and changes its mode respectively. Valid Modes: adduser, addgroup. --uid ID Force the new userid to be the given number. adduser will fail if the userid is al‐ ready taken. Valid Modes: adduser, adduser --system." }, { "flag": "", "long": "--verbose", "arg": null, "description": "Synonymous to --stdoutmsglevel=info. Deprecated. --stdoutmsglevel prio --stderrmsglevel prio --logmsglevel prio Minimum priority for messages logged to syslog/journal and the console, respectively. Values are trace, debug, info, warn, err, and fatal. Messages with the priority set here or higher get printed to the respective medium. Messages printed to stderr are not repeated on stdout. That allows the local admin to control adduser's chattiness on the console and in the log independently, keeping probably confusing information to itself while still leaving helpful information in the log." }, { "flag": "-v", "long": "--version", "arg": null, "description": "Display version and copyright information." } ], "examples": [], "see_also": [ { "name": "adduser.conf", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/adduser.conf/5/json" }, { "name": "deluser", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/deluser/8/json" }, { "name": "groupadd", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/groupadd/8/json" }, { "name": "useradd", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/useradd/8/json" }, { "name": "usermod", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/usermod/8/json" } ] }