|Main index||Section 8||日本語||Options|
|Login name. The user name is restricted to whatever pw(8) will accept. Generally this means it may contain only lowercase characters or digits but cannot begin with the ‘-’ character. Maximum length is 16 characters. The reasons for this limit are historical. Given that people have traditionally wanted to break this limit for aesthetic reasons, it has never been of great importance to break such a basic fundamental parameter in Unix . You can change UT_NAMESIZE in <utmp.h> and recompile the world; people have done this and it works, but you will have problems with any precompiled programs, or source that assumes the 8-character name limit, such as NIS. The NIS protocol mandates an 8-character username. If you need a longer login name for e-mail addresses, you can define an alias in /etc/mail/aliases.|
|This is typically known as the gecos field and usually contains the user's full name. Additionally, it may contain a comma separated list of values such as office number and work and home phones. If the name contains an ampersand it will be replaced by the capitalized login name when displayed by other programs. The ‘amp;:’ character is not allowed.|
|UID||Automatically generated or your choice. It must be less than 32000.|
|Automatically generated or your choice. It must be less than 32000.|
|You may choose an empty password, disable the password, use a randomly generated password or specify your own plaintext password, which will be encrypted before being stored in the user database.|
For a shared area you create a separate UID/GID, you place each person that should be able to access this area into that new group.
This model of UID/GID administration allows far greater flexibility than lumping users into groups and having to muck with the umask when working in a shared area.
I have been using this model for almost 10 years and found that it works for most situations, and has never gotten in the way. (Rod Grimes)
Create new configuration file and exit.
This option is mutually exclusive with the
|Home partition. Default partition, under which all user directories will be located. The /nonexistent partition is considered special. The adduser script will not create and populate a home directory by that name. Otherwise, by default it attempts to create a home directory.|
|Do not attempt to create the home directory.|
Disable the account.
This option will lock the account by prepending the string
to the password field.
The account may be unlocked
by the super-user with the
|Get the list of accounts to create from file. If file is "-", then get the list from standard input. If this option is specified, adduser will operate in batch mode and will not seek any user input. If an error is encountered while processing an account, it will write a message to standard error and move to the next account. The format of the input file is described below.|
|Normally, if no login group is specified, it is assumed to be the same as the username. This option makes login_group the default.|
|Space-separated list of additional groups. This option allows the user to specify additional groups to add users to. The user is a member of these groups in addition to their login group.|
|Print a summary of options and exit.|
|Copy files from directory into the home directory of new users; dot.foo will be renamed to .foo.|
|Set default login class.|
|Send new users a welcome message from file. Specifying a value of no for file causes no message to be sent to new users. Please note that the message file can reference the internal variables of the adduser script.|
|Create the home directory with permissions set to mode.|
|Do not read the default configuration file.|
|Minimal user feedback. In particular, the random password will not be echoed to standard output.|
Default shell for new users.
argument may be the base name of the shell or the full path.
|The existence or validity of the specified shell will not be checked.|
|Use UIDs from uid on up.|
|Password type. The adduser utility allows the user to specify what type of password to create. The type argument may have one of the following values:|
|no||Disable the password. Instead of an encrypted string, the password field will contain a single ‘*’ character. The user may not log in until the super-user manually enables the password.|
|none||Use an empty string as the password.|
|yes||Use a user-supplied string as the password. In interactive mode, the user will be prompted for the password. In batch mode, the last (10th) field in the line is assumed to be the password.|
|Generate a random string and use it as a password. The password will be echoed to standard output. In addition, it will be available for inclusion in the message file in the randompass variable.|
|name||Login name. This field may not be empty.|
|uid||Numeric login user ID. If this field is left empty, it will be automatically generated.|
|gid||Numeric primary group ID. If this field is left empty, a group with the same name as the user name will be created and its GID will be used instead.|
|class||Login class. This field may be left empty.|
This field denotes the password change date for the account.
The format of this field is the same as the format of the
|expire||Account expiration. This field denotes the expiry date of the account. The account may not be used after the specified date. The format of this field is the same as that for password ageing. This field may be left empty to turn it off.|
|gecos||Full name and other extra information about the user.|
|Home directory. If this field is left empty, it will be automatically created by appending the username to the home partition. The /nonexistent home directory is considered special and is understood to mean that no home directory is to be created for the user.|
|shell||Login shell. This field should contain either the base name or the full path to a valid login shell.|
This field should contain a plaintext string, which will
be encrypted before being placed in the user database.
If the password type is
and this field is empty, it is assumed the account will have an empty password.
If the password type is
and this field is
empty, its contents will be used
as a password.
This field will be ignored if the
|/etc/login.conf||login classes database|
|/etc/adduser.conf||configuration file for adduser|
|message file for adduser|
|/usr/share/skel||skeletal login directory|
|/var/log/adduser||logfile for adduser|
Also, password ageing and account expiry times are currently settable only in batch mode or when specified in /etc/adduser.conf. The user should be able to set them in interactive mode as well.
|ADDUSER (8)||September 15, 2012|
|Main index||Section 8||日本語||Options|
|“||F U cn rd dis U mst uz Unix.||”|