Use the userdel command to remove a local Linux user account: an administrator can run sudo userdel alice. To remove the account and its home directory, use sudo userdel -r alice, but check the files and services first because that option can permanently delete user data.
What userdel removes
userdel is a system administration command for deleting a user account from the local system’s account records. It removes the account entry and related account information managed by the command on that Linux distribution. It does not necessarily erase every file owned by the user, stop every process, remove access from remote systems, or undo changes made by other software.
A Linux account is more than a name and password. The system associates a username with a numeric user ID, a primary group, a home directory, and a login shell. Applications and services may also refer to the account or its numeric ID. Removing an account therefore requires more thought than simply deleting a line or directory.
Account-management tools and their exact behavior can vary by distribution and local configuration. Consult the command’s local manual page, typically with man userdel, and follow your organization’s administration procedures before changing a production machine.
Choose whether to keep the home directory
The main choice is whether to preserve the user’s files. Without -r, userdel ordinarily removes the account but leaves the home directory and the user’s mail spool in place. Keeping those files can be useful when an account is being retired but its documents or configuration may still be needed.
With -r, the command attempts to remove the home directory and mail spool as well. This is a destructive option: files that exist only there may be lost. It does not mean “find every file belonging to this user and delete it everywhere.” Files stored elsewhere can remain, and the command’s handling of paths depends on system configuration.
- Keep data:
sudo userdel alice - Remove the account and its home directory:
sudo userdel -r alice
Replace alice with the actual login name, not a display name. Avoid adding -r until you have confirmed that the data is backed up or no longer needed.
Prepare before deleting an account
Before running the command, establish that you have authority to remove the account and that it is the correct one. A mistaken deletion can disrupt interactive access, scheduled work, application ownership, or a service that runs under a dedicated account.
- Confirm the exact username and whether it is a local account.
- Ask whether its files, running jobs, or service access must be retained.
- Check whether the account is currently logged in or has active processes.
- Back up or transfer important files before choosing removal of the home directory.
- Identify scheduled tasks, services, and access on other machines that may rely on it.
For a departing employee or a shared server account, deletion may be only one part of offboarding. You may also need to revoke credentials, remove group memberships, disable keys, update service configuration, and check access to network resources. The appropriate sequence depends on local policy and the systems involved.
Run userdel and verify the result
For a straightforward local account, use a privileged shell or prefix the command with sudo. For example, sudo userdel alice removes the account while normally leaving its home directory. If data removal is approved, sudo userdel -r alice requests removal of the home directory and mail spool too.
Afterward, verify the account is no longer present using the system’s account lookup tools, such as getent passwd alice. If the command returns an entry, the account may still be available through a directory service or another account source rather than the local files alone. Check the relevant identity-management system instead of repeatedly running userdel.
If the home directory was meant to remain, inspect its ownership and contents before moving or reassigning anything. If it was meant to be deleted, verify the intended path and check for remaining files elsewhere. Do not assume that an account lookup alone confirms all related access has been removed.
Processes, files, and scheduled work
An account can have processes running when you try to remove it. The command may refuse to delete an account with active processes, and forcing a deletion does not automatically make those processes harmless or clean up their files. Identify the process owner and determine what the processes do before stopping them. On a shared or production system, avoid killing processes solely because their owner’s account is being removed.
Files outside the home directory may still be owned by the account’s numeric user ID. Examples include files in application data directories, temporary locations, or shared storage. After deletion, a file may display a numeric owner instead of a username. That does not mean the file has vanished; it means the system no longer maps that ID to the removed account name.
Scheduled tasks and service definitions need separate attention. A cron job, system service, or application may refer to the username, and deleting the account does not guarantee that every such reference is removed. Review local configuration and logs according to your system’s procedures. If the account runs a service, plan an orderly migration or shutdown before deleting it.
Common errors and what they mean
An error saying the user is currently in use usually points to an active session or process. Check logins and process ownership, then decide whether to wait, stop a service cleanly, or end a session under your normal administrative process. Do not use a force option as a shortcut without understanding its effects.
A message that the user does not exist can mean a typo, a different account name, or that the account is managed outside the local account files. A user obtained from a network directory may not be deletable with userdel; remove or disable it through the system that manages that identity.
A home-directory removal error may indicate that files could not be deleted or that the directory is not the path expected by the command. Check the account’s configured home directory and the exact error. If the account was removed but files remain, deal with those files deliberately rather than using broad deletion commands that could affect another user’s data.
Local accounts and central identity services
userdel is intended for local account administration, commonly on systems where accounts are managed through local tools and files. Linux machines can also obtain users from centrally managed identity services. In that case, an account may appear in login lookups even though its record is not stored locally.
Deleting a local entry does not remove a centrally managed identity. Likewise, removing an identity from a directory service does not necessarily remove local files or terminate existing sessions on every machine. Determine the source of the account before taking action. If the system participates in an organization’s identity-management setup, use its documented workflow and coordinate changes across affected machines.
Alternatives to immediate deletion
Deletion is not always the best first step. If you need to prevent login while preserving data for review, consider locking or disabling the account using the tools supported by the distribution. That can provide time to transfer files, inspect dependencies, or confirm that access has been revoked. Locking methods and their effect on different login routes vary, so verify the local behavior rather than treating a locked password as a universal block on all access.
Another option is to change account credentials or remove particular access paths while leaving the account available for a service that still needs it. For an account that owns a running application, migrating the service to a dedicated replacement account may be safer than deleting its current owner immediately. Choose an approach based on whether the goal is to prevent interactive login, preserve records, or remove the identity entirely.
Frequently Asked Questions
Does userdel delete the user’s files?
Not all of them. Without -r, the home directory is normally retained. With -r, the command attempts to remove the home directory and mail spool, but files elsewhere may remain.
What is the difference between userdel and userdel -r?userdel removes the account while usually preserving its home directory and mail spool. The -r option also requests removal of those locations, so use it only after checking that their contents are no longer needed.
Can I delete a user who is logged in?
The command may refuse when the account has active processes. Check sessions and processes, and handle them according to the service or system’s normal procedure before trying again.
Why does the username still appear after userdel?
The account may come from a central identity service, a different account source, or a cached lookup. Check where the system obtains users and verify the account through that source.
Will userdel remove files owned by the account everywhere?
No. Files outside the home directory can remain and may show a numeric owner ID after deletion. Locate and review such files carefully; do not delete them automatically without confirming their purpose.
Key point
Use sudo userdel username to remove a local account while generally retaining its home directory, or add -r when removing that data is intentional. Confirm the account source, check processes and dependencies, preserve needed files, and verify the result through the system that manages the identity.