Delete an Account Deliberately

The practice assistant is leaving, and the account is no longer required. Removing an account record and cleaning up its resources are related tasks, but not the same task. Files, running processes and service configuration can outlive a username.

We will use userdel to understand account removal first. Resist the idea that one deletion command automatically finds and erases every item associated with a person. A professional cleanup plan starts by deciding what must be retained, transferred or revoked.

Prepare the example

Work only in a disposable VM with the practice account, not your own login or a real staff account. Confirm the target identity and handle active use appropriately. The example omits -r so we can distinguish removal of the account record from explicit home-directory cleanup.

Bash · Linux terminal

sudo userdel school-assistant
getent passwd school-assistant

Expected behavior; machine-dependent details

No record if deletion succeeded; getent returns nonzero for the missing key.

sudo userdel school-assistant asks the system to remove the account under the utility's rules. The follow-up getent lookup should no longer return that user record through the configured account sources when the local deletion applies as intended. A missing lookup result is expected here, rather than a reason to recreate the account immediately.

Files store numeric ownership identifiers, so removing the name does not erase every owned file across storage. The -r option explicitly requests home and mail removal, but even that is not universal cleanup of all resources. Tools may refuse removal while the user is in use; address the situation rather than applying force without understanding it.

Deleting a user account removes its login identity from the system, but you must decide separately what should happen to that user's home directory and files.

Open a terminal before removing an account

You can open the terminal using Ctrl + Alt + T, or search for "Terminal" in your application menu.

Step 2: Check Existing Users

Before deleting a user, you might want to check who exists on the system.

cut -d: -f1 /etc/passwd

root
daemon
bin
sys
john
testuser

Here, we see a list of user accounts. Let's say we want to delete testuser.

Step 3: Delete the User

To delete a user, use the userdel command. You’ll need superuser (admin) privileges, so either log in as root or use sudo.

sudo userdel testuser

This removes the user from the system, but their files in the home directory still remain.

Step 4: Delete User and Home Directory (Optional)

If you want to remove the user and their home directory at the same time, use the -r option:

sudo userdel -r testuser

This will delete:

• The user account
• The user's home directory (like /home/testuser)
• Mail spool and other user-owned files in typical locations

Step 5: Confirm Deletion

You can check if the user was deleted successfully:

id testuser

id: ‘testuser’: no such user

If you see that message, it means the user is gone!

Wrap Up

And that’s it! You’ve just learned how to delete a user from your Linux system.

To quickly recap:

1. Use userdel to remove a user
2. Add -r to also remove their home directory
3. Always check with id username to confirm

Your task: Does userdel without -r erase every file the user owned?

Work only in a disposable VM with the practice account, not your own login or a real staff account. Confirm the target identity and handle active use appropriately. The example omits -r so we can distinguish removal of the account record from explicit home-directory cleanup.

Bash · complete example for this question

sudo userdel school-assistant
getent passwd school-assistant

Expected behavior; machine-dependent details

No record if deletion succeeded; getent returns nonzero for the missing key.

Worked answer

No; account removal and data cleanup are distinct.

No, ordinary account deletion does not automatically purge every file the person owned. Record removal, home cleanup, data transfer and session handling need separate decisions. Retaining a report may be the correct outcome even though retaining the person's login is not.

Confirm which identity is being removed and what resources should survive. Account records, numeric file ownership and running activity are separate parts of the system. Do not use a broad cleanup option before deciding whether that home contains records someone still needs.