This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
A user is a name, a home, a shell, and the groups the ticket already chose. useradd does not decide those for you. The builder drafts the command. The bulk generator drafts a loop from names you typed. Neither tool creates an account.
A password on the command line lands in the shell history. Use prompt-for-this in the note and set the password through the path your standard already uses, later, on a host you administer. Do not invent a shared default password.
Do not create accounts on a host you do not administer. Do not add the new user to every group because the list was long. One extra group is a decision. Lock and modify are a later page.
192.0.2.10/24 and example.com are documentation. They stay in the note.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Write the username, the home, the shell, and the groups.
- Draft useradd.
- Confirm the password is not in the command.
- If the list is long, draft the bulk script and read every name.
- Do not run it during the reading.
- Stop after this list.
Mistakes that outlive the command
How to Add Users in Linux goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A password on the command line.
- A shared default password.
- A host you do not administer.
- Every group granted at once.
- Running the bulk script during the reading.
Decisions to write down
One decision for How to Add Users in Linux: The names are people you meant. The shell is the one you chose. The password is absent from the command. The host is yours. And the script was not run yet.
Checks before you call it done
Confirm this before you call the change done: Each username is written. Home and shell are written. No password is in the draft. The host is named. And the command was not run during the reading. If one of those fails, stop.
# useradd drafts only.
# prompt-for-this is not a password on the command line.Before you leave the host
How to Add Users in Linux ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.