PW(8)

πŸ“¦
version 15.1 Β· 2 versions
, in freebsd 15.1

πŸ’– PW(8) β€” create, remove, modify & display system users and groups

Okay bestie, welcome to the System Manager's Manual page for PW(8) β€” aka the pw command, aka your command-line editor for system users and groups. It's giving admin-girlie main character energy πŸ‘‘βœ¨


🌸 NAME

pw β€” create, remove, modify & display system users and groups


✨ SYNOPSIS

       pw [-M metalog] [-R rootdir] [-V etcdir] useradd [-n] name [-mNoPq]
          [-C config] [-c comment] [-d homedir] [-e accexpdate] [-G grouplist]
          [-g group] [-H fd] [-h fd] [-k skeldir] [-L class] [-M mode]
          [-p passexpdate] [-s shell] [-u uid] [-w passmethod]
          [-Y [-y nispasswd]]
       pw [-R rootdir] [-V etcdir] useradd -D [-q] [-b basehome] [-C config]
          [-e accexpdays] [-G grouplist] [-g group] [-i mingid,maxgid]
          [-k skeldir] [-M mode] [-p passexpdays] [-s shell] [-u minuid,maxuid]
          [-w passmethod] [-Y [-y nispasswd]]
       pw [-R rootdir] [-V etcdir] userdel [-n] name|[-u] uid [-r]
          [-Y [-y nispasswd]]
       pw [-R rootdir] [-V etcdir] usermod [-n] name|uid [-u newuid] | -u uid
          [-mNPq] [-C config] [-c comment] [-d homedir] [-e accexpdate]
          [-k skeldir] [-G grouplist] [-g group] [-H fd] [-h fd] [-L class]
          [-l newname] [-M mode] [-p passexpdate] [-s shell] [-w passmethod]
          [-Y [-y nispasswd]]
       pw [-R rootdir] [-V etcdir] usershow [-n] name|[-u] uid [-7aFP]
       pw [-R rootdir] [-V etcdir] usernext [-q] [-C config]
       pw [-R rootdir] [-V etcdir] groupadd [-n] name [-oNPqY] [-C config]
          [-g gid] [-H fd] [-h fd] [-M members]
       pw [-R rootdir] [-V etcdir] groupdel [-n] name|[-g] gid [-Y]
       pw [-R rootdir] [-V etcdir] groupmod [-n] name|gid [-g newgid] | -g gid
          [-NPqY] [-C config] [-d oldmembers] [-H fd] [-h fd] [-l newname]
          [-M members] [-m newmembers]
       pw [-R rootdir] [-V etcdir] groupshow [-n] name|[-g] gid [-aFP]
       pw [-R rootdir] [-V etcdir] groupnext [-C config] [-q]
       pw [-R rootdir] [-V etcdir] lock [-n] name|[-u] uid [-q] [-C config]
       pw [-R rootdir] [-V etcdir] unlock [-n] name|[-u] uid [-q] [-C config]

πŸ’… DESCRIPTION

Okay so the pw utility is a command-line based editor for the system user and group files. It lets the superuser add, modify, and remove users and groups in an easy-to-use, standardized way. That's literally the whole vibe πŸ’…

Big important note: pw only operates on the local user and group files. NIS users and groups must be maintained on the NIS server. No cap 🫢

The pw utility handles updating the passwd(5), master.passwd(5), group(5) and the secure and insecure password database files, and it must be run as root (except when using -R or -V).

🚨 Root check, bestie: pw must be run as root, except when using -R or -V.

The first one or two keywords provided to pw on the command line provide the context for the remainder of the arguments. The keywords user and group may be combined with add, del, mod, show, or next in any order. (For example, showuser, usershow, show user, and user show all mean the same thing.) This flexibility is useful for interactive scripts calling pw for user and group database manipulation. Following these keywords, the user or group name or numeric id may be optionally specified as an alternative to using the -n name, -u uid, -g gid options.

🌟 the common flags (most or all modes)

The following flags are common to most or all modes of operation:

  • -R rootdir β€” Specifies an alternate root directory within which pw will operate. Any paths specified will be relative to rootdir.
  • -V etcdir β€” Set an alternate location for the password, group, and configuration files. Can be used to maintain a user/group database in an alternate location. If this switch is specified, the system /etc/pw.conf will not be sourced for default configuration data, but the file pw.conf in the specified directory will be used instead (or none, if it does not exist). The -C flag may be used to override this behaviour.
⚠️ Exception alert: as an exception to the general rule where options must follow the operation type, the -V flag must be used on the command line before the operation keyword. Periodt.
  • -C config β€” By default, pw reads the file /etc/pw.conf to obtain policy information on how new user accounts and groups are to be created. The -C option specifies a different configuration file. While most of the contents of the configuration file may be overridden via command-line options, it may be more convenient to keep standard information in a configuration file.
  • -q β€” Use of this option causes pw to suppress error messages, which may be useful in interactive environments where it is preferable to interpret status codes returned by pw rather than messing up a carefully formatted display.
  • -N β€” This option is available in add and modify operations, and tells pw to output the result of the operation without updating the user or group databases. You may use the -P option to switch between standard passwd and readable formats.
  • -Y β€” Using this option with any of the update modes causes pw to run make(1) after changing to the directory /var/yp. This is intended to allow automatic updating of NIS database files. If separate passwd and group files are being used by NIS, then use the -y nispasswd option to specify the location of the NIS passwd database so that pw will concurrently update it with the system password databases.

πŸ‘‘ USER OPTIONS

The following options apply to the useradd and usermod commands:

  • [-n] name β€” Required unless -u uid is given. Specify the user/account name. In the case of usermod can be a uid.
  • -u uid β€” Required if name is not given. Specify the user/account numeric id. In the case of usermod if paired with name, changes the numeric id of the named user/account.

Usually, only one of these options is required, as the account name will imply the uid, or vice versa. However, there are times when both are needed. For example, when changing the uid of an existing user with usermod, or overriding the default uid when creating a new account with useradd. To automatically allocate the uid to a new user with useradd, then do not use the -u option. Either the account or userid can also be provided immediately after the useradd, userdel, usermod, or usershow keywords on the command line without using the -n or -u options.

  • -c comment β€” This field sets the contents of the passwd GECOS field, which normally contains up to four comma-separated fields containing the user's full name, office or location, and work and home phone numbers. These sub-fields are used by convention only, however, and are optional. If this field is to contain spaces, the comment must be enclosed in double quotes ". Avoid using commas in this field as these are used as sub-field separators, and the colon : character also cannot be used as this is the field separator for the passwd file itself.
  • -d homedir β€” This option sets the account's home directory. Normally, this is only used if the home directory is to be different from the default determined from /etc/pw.conf β€” normally /home with the account name as a subdirectory.
  • -e accexpdate β€” Set the account's expiration date. Format of the date is either a UNIX time in decimal, or a date in dd-mmm-yy[yy] format, where dd is the day, mmm is the month, either in numeric or alphabetic format ('Jan', 'Feb', etc) and year is either a two or four digit year. This option also accepts a relative date in the form +n[mhdwoy] where n is a decimal, octal (leading 0) or hexadecimal (leading 0x) digit followed by the number of Minutes, Hours, Days, Weeks, Months or Years from the current date at which the expiration date is to be set.
  • -p passexpdate β€” Set the account's password expiration date. This field is similar to the account expiration date option, except that it applies to forced password changes. This is set in the same manner as the -e option.
  • -g group β€” Set the account's primary group to the given group. group may be defined by either its name or group number.
  • -G grouplist β€” Set secondary group memberships for an account. grouplist is a comma, space, or tab-separated list of group names or group numbers. The user is added to the groups specified in grouplist, and removed from all groups not specified. The current login session is not affected by group membership changes, which only take effect when the user reconnects.
🫢 Tiny but important note: do not add a user to their primary group with grouplist.
  • -L class β€” This option sets the login class for the user being created. See login.conf(5) and passwd(5) for more information on user login classes.
  • -m β€” This option instructs pw to attempt to create the user's home directory. While primarily useful when adding a new account with useradd, this may also be of use when moving an existing user's home directory elsewhere on the file system. The new home directory is populated with the contents of the skeleton directory, which typically contains a set of shell configuration files that the user may personalize to taste. Files in this directory are usually named dot.⟨config⟩ where the dot prefix will be stripped. When -m is used on an account with usermod, existing configuration files in the user's home directory are not overwritten from the skeleton files.

When a user's home directory is created, it will by default be a subdirectory of the basehome directory as specified by the -b option, bearing the name of the new account. This can be overridden by the -d option on the command line, if desired.

  • -M metalog β€” okay so this -M is lowkey doing double duty πŸ’…. Give it a path to an mtree(5) metalog file and pw will add entries for all files added to a user's home directory. This is useful when building images as a non-root user, because the metalog can be used as input to tar(1) or makefs(8). Heads up: this option must precede the useradd string on the command line, otherwise it will be interpreted as the mode option. iykyk.
  • -M mode β€” create the user's home directory with the specified mode, modified by the current umask(2). If omitted, it is derived from the parent process's umask(2). This option is only useful in combination with the -m flag.
  • -k skeldir β€” set the skeleton directory, from which basic startup and configuration files are copied when the user's home directory is created. This option only has meaning when used with the -d or -m flags.
  • -s shell β€” set or change the user's login shell to shell. If the path to the shell program is omitted, pw searches the shellpath specified in /etc/pw.conf and fills it in as appropriate. Note: unless you have a specific reason to do so, you should avoid specifying the path β€” this lets pw validate that the program exists and is executable. Specifying a full path (or supplying a blank "" shell) avoids this check and allows for such entries as /nonexistent that should be set for accounts not intended for interactive login.
  • -h fd β€” this option provides a special interface by which interactive scripts can set an account password using pw. Because the command line and environment are fundamentally insecure mechanisms by which programs can accept information, pw will only allow setting of account and group passwords via a file descriptor (usually a pipe between an interactive script and the program). sh, bash, ksh and perl all possess mechanisms by which this can be done. Alternatively, pw will prompt for the user's password if -h 0 is given, nominating stdin as the file descriptor on which to read the password. Note that this password will be read only once and is intended for use by a script rather than for interactive use. If you wish to have new password confirmation along the lines of passwd(1), this must be implemented as part of an interactive script that calls pw.

Also: if a value of - is given as the argument fd, then the password will be set to *, rendering the account inaccessible via password-based login. Iconic safety era.

  • -H fd β€” read an encrypted password string from the specified file descriptor. This is like -h, but the password should be supplied already encrypted in a form suitable for writing directly to the password database. See openssl-passwd(1) and crypt(3) for more details about generating an encrypted password hash.

It is possible to use useradd to create a new account that duplicates an existing user id. While this is normally considered an error and will be rejected, the -o option overrides the check for uniqueness and allows the duplication of the uid. This may be useful if you allow the same user to login under different contexts (different group allocations, different home directory, different shell) while providing basically the same permissions for access to the user's files in each account. Main character uid energy, honestly.

The useradd command also has the ability to set new user and group defaults by using the -D option. Instead of adding a new user, pw writes a new set of defaults to its configuration file, /etc/pw.conf. When using the -D option, you must not use either -n name or -u uid or an error will result. Use of -D changes the meaning of several command line switches in the useradd command. These are:

  • -D β€” set default values in /etc/pw.conf configuration file, or a different named configuration file if the -C config option is used.
  • -b basehome β€” set the root directory in which user home directories are created. The default value for this is /home, but it may be set elsewhere as desired.
  • -e accexpdays β€” set the default account expiration period in days. When -D is used, the accexpdays argument is interpreted differently. It must be numeric and represents the number of days after creation that the account expires. A value of 0 suppresses automatic calculation of the expiry date.
  • -p passexpdays β€” set the default password expiration period in days. When -D is used, the passexpdays argument is interpreted differently. It must be numeric and represents the number of days after creation that the account expires. A value of 0 suppresses automatic calculation of the expiry date.
  • -g group β€” set the default group for new users. If a blank group is specified using -g "", then new users will be allocated their own private primary group with the same name as their login name. If a group is supplied, either its name or uid may be given as an argument.
  • -G grouplist β€” set the default groups in which new users are granted membership. This is a separate set of groups from the primary group. Avoid nominating the same group as both primary and extra groups. In other words, these extra groups determine membership in groups other than the primary group. grouplist is a comma-separated list of group names or ids, and are always stored in /etc/pw.conf by their symbolic names.
  • -L class β€” this option sets the default login class for new users.
  • -k skeldir β€” set the default skeleton directory, from which prototype shell and other initialization files are copied when pw creates a user's home directory. See description of -k for naming conventions of these files.
  • -u minuid,maxuid, -i mingid,maxgid β€” set the minimum and maximum user and group ids allocated for new accounts and groups created by pw. The default values for each is 1000 minimum and 32000 maximum. minuid and maxuid are both numbers, where max must be greater than min, and both must be between 0 and 32767 (the same applies to mingid and maxgid). In general, user and group ids less than 100 are reserved for use by the system, and numbers greater than 32000 may also be reserved for special purposes (used by some system daemons). Also, uids and gids between 100 and 999 are commonly used by pseudo-users associated with third-party programs, and generally should be avoided when assigning normal users. Do not pick chaos numbers, bestie.
  • -w passmethod β€” the -w option selects the default method used to set passwords for newly created user accounts. passmethod is one of:
    • no β€” disable login on newly created accounts
    • yes β€” force the password to be the account name
    • none β€” force a blank password
    • random β€” generate a random password

The random or no methods are the most secure; in the former case, pw generates a password and prints it to stdout, which is suitable when users are issued passwords rather than being allowed to select their own (possibly poorly chosen) password. The no method requires that the superuser use passwd(1) to render the account accessible with a password. Security slay.

  • -y path β€” this sets the pathname of the database used by NIS if you are not sharing the information from /etc/master.passwd directly with NIS. You should only set this option for NIS servers.

The userdel command has three distinct options. The -n name and -u uid options have already been covered above. The additional option is:

  • -r β€” this tells pw to remove the user's home directory and all of its contents. The pw utility errs on the side of caution when removing files from the system. Firstly, it will not do so if the uid of the account being removed is also used by another account on the system, and the β€œhome” directory in the password file is a valid path that commences with the character /. Secondly, it will only remove files and directories that are actually owned by the user, or symbolic links owned by anyone under the user's home directory. Finally, after deleting all contents owned by the user only empty directories will be removed. If the home directory is a ZFS dataset and has been emptied, the dataset will be destroyed. ZFS datasets within the home directory and snapshots are not handled. If any additional cleanup work is required, this is left to the administrator. This one is serious business β€” cute but careful.

Mail spool files and crontab(5) files are always removed when an account is deleted as these are unconditionally attached to the user name. Jobs queued for processing by at(1) are also removed if the user's uid is unique and not also used by another account on the system.

The usermod command adds one additional option:

  • -l newname β€” this option allows changing of an existing account name to newname. The new name must not already exist, and any attempt to duplicate an existing account name will be rejected.

The usershow command allows viewing of an account in one of two formats. By default, the format is identical to the format used in /etc/master.passwd with the password field replaced with a *. If the -P option is used, then pw outputs the account details in a more human readable form. If the -7 option is used, the account details are shown in v7 format. The -a option lists all users currently on file. Using -F forces pw to print the details of an account even if it does not exist. ✨ account reveal era ✨

usernext hands you back the next available user and group ids, separated by a colon. Ngl this one's basically only for interactive scripts or front-ends that are driving pw around β€” if that's not you, you can skip it πŸ’…

🌸 GROUP OPTIONS 🌸

The -C and -q options (they got explained at the start of the previous section, go peek) work with the group manipulation commands too. Other options that all the group-related commands share:

  • [-n] name β€” required unless -g gid is given. It's the group name you want. With groupmod it can also be a gid.
  • -g gid β€” required if name isn't given. This is the group's numeric id. With groupmod, if you pair it with name, it changes the numeric id of the named group.

Same energy as the account name and id fields: usually you only need to give one of them, since the group name implies the uid and vice versa. The only times you'd need both are when you're setting a specific group id against a brand new group, or when you're changing the uid of a group that already exists.

  • -M memberlist β€” a whole other way to add existing users to a new group (that's in groupadd) or to replace an existing membership list (in groupmod). memberlist is a comma-, space-, or tab-separated list of valid, already-existing user names or uids.
  • -m newmembers β€” like -M's cousin: lets you add existing users to a group without wiping the existing member list. Login names or user ids both work, and duplicates just get silently eliminated. so chill 🫢
  • -d oldmembers β€” also like -M, but for deletion: it removes existing users from a group without replacing the whole existing member list. Login names or user ids both work here too, and duplicates get silently eliminated.

groupadd also has an -o option, which lets you allocate a group id that already exists to a new group. Default behavior is to reject an attempt to add a group, and this option overrides that duplicate-gid check. Fr there's rarely any need to duplicate a gid β€” like why would you 😭

The groupmod command throws in one extra option of its own:

  • -l newname β€” lets you rename an existing group to newname. The new name must not already exist, and literally any attempt to duplicate an existing group name gets rejected. no cap.

Options for groupshow are the same as for usershow, except it's -g gid instead of -u uid to specify the group id. Heads up: the -7 option does not apply to the groupshow command. 🚫

And the command groupnext returns the next available group id on standard output. slay ✨


πŸ”’ USER LOCKING πŸ”’

pw supports a simple, lowkey password locking mechanism for users. It works by prepending the string β€˜*LOCKED*’ to the beginning of the password field in master.passwd(5) β€” which is what stops authentication from succeeding. iconic behavior honestly.

The lock and unlock commands take a user name or uid of the account you want to lock or unlock, respectively. The -V, -C, and -q options, as described above, are accepted by these commands too.

πŸ’œ NOTES πŸ’œ

Want a summary of the options available with each command? Just run:

pw [command] help

For example:

pw useradd help

...lists every available option for the useradd operation. iykyk, this is the cheat sheet πŸŽ€

Okay so here's the 8-bit character tea β˜•: pw allows 8-bit characters in the passwd GECOS field (that's the user's full name, office, work and home phone number subfields), but it disallows them in user login and group names. Use 8-bit characters with caution, bestie β€” connecting to the Internet will require that your mail transport program supports 8BITMIME, and it will convert headers containing 8-bit characters to 7-bit quoted-printable format. sendmail(8) does support this. Use of 8-bit characters in the GECOS field should be used in conjunction with the user's default locale and character set, and should not be implemented without their use. Using 8-bit characters may also affect other programs that transmit the contents of the GECOS field over the Internet, such as fingerd(8), plus a small number of TCP/IP clients, such as IRC, where full names specified in the passwd file may be used by default. πŸ’€

pw writes a log to the /var/log/userlog file whenever actions like user or group additions or deletions happen. The location of this logfile can be changed in pw.conf(5). cute and traceable πŸ¦‹

πŸŽ€ FILES πŸŽ€

  • /etc/master.passwd β€” The user database
  • /etc/passwd β€” A Version 7 format password file
  • /etc/login.conf β€” The user capabilities database
  • /etc/group β€” The group database
  • /etc/pw.conf β€” Pw default options file
  • /var/log/userlog β€” User/group modification logfile

⭐ EXAMPLES ⭐

Add a new user Glurmo Smith (gsmith). A gsmith login group gets created if it's not already there. The login shell is set to csh(1). A new home directory at /home/gsmith gets created if it doesn't already exist. Finally, a random password is generated and displayed β€” main character behavior 🌈:

pw useradd -n gsmith -c "Glurmo Smith" -s csh -m -w random

Delete the gsmith user and their home directory, including contents. bye bestie πŸ‘‹:

pw userdel -n gsmith -r

Add the existing user jsmith to the wheel group, on top of all the other groups jsmith is already a member of:

pw groupmod wheel -m jsmith

Generate a random password and show it in both plain text and encrypted form β€” without modifying any database. just looking respectfully πŸ™ˆ:

pw usermod nobody -Nw random

πŸ’… EXIT STATUS πŸ’…

pw returns EXIT_SUCCESS on a successful operation. Otherwise it returns one of these exit codes, defined by sysexits(3):

EX_USAGE

  • Command line syntax errors (invalid keyword, unknown option).

EX_NOPERM

  • Attempting to run one of the update modes as non-root.

EX_OSERR

  • Memory allocation error.
  • Read error from password file descriptor.

EX_DATAERR

  • Bad or invalid data provided or missing on the command line or via the password file descriptor.
  • Attempted to remove, rename root account or change its uid.

EX_OSFILE

  • Skeleton directory is invalid or does not exist.
  • Base home directory is invalid or does not exist.
  • Invalid or non-existent shell specified.

EX_NOUSER

  • User, user id, group or group id specified does not exist.
  • User or group recorded, added, or modified unexpectedly disappeared.

EX_SOFTWARE

  • No more group or user ids available within specified range.

EX_IOERR

  • Unable to rewrite configuration file.
  • Error updating group or user database files.
  • Update error for passwd or group database files.

EX_CONFIG

  • No base home directory configured.

🧚 SEE ALSO 🧚

chpass(1), passwd(1), umask(2), group(5), login.conf(5), passwd(5), pw.conf(5), groups(7), pwd_mkdb(8), vipw(8), zfs(8)

πŸ‘‘ HISTORY πŸ‘‘

The pw utility was written to mimic many of the options used in the SYSV shadow support suite, but it's modified for the passwd and group fields specific to the 4.4BSD operating system, and it combines all of the major elements into a single command. one command to rule them all, periodt πŸ’–


okay that's the whole page bestie, you made it πŸŽ‰ this gem is from the Debian edition of the page, dated April 19, 2026, and yes it's the PW(8) page β€” go forth and manage your users responsibly, ily 🫢✨

πŸ“¦ where this page comes from
  • freebsd 15.1: base 15.1
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms