📚 Table of Contents
- The Real World Problem
- Today’s Mission
- Commands I Used
- RHCSA Objectives Covered
- What I Learned (the hard way)
- Tomorrow’s Challenge Teaser
The Real World Problem
You’ve got a shiny new junior dev on the team. They need sudo access to restart a service... and next thing you know, your web server is down and /etc/ is crying.
Today’s challenge: Give the right people the right power—without accidentally handing them the keys to the kingdom.
Today’s Mission
Add a user to the wheel group (aka: the VIP club for sudo users)
Check who else has sudo rights
Configure sudo access safely via /etc/sudoers
Bonus: Set up a custom sudo rule for a specific command (if you're feeling spicy!)
Commands I Used
Checked the sacred scrolls of sudo:
(Seriously, use visudo, not your usual editor—it’s got safety checks so you don’t accidentally break your entire system trying to be helpful.)
RHCSA Objectives Covered
Manage local user security
Configure sudo access
Understand /etc/sudoers and the wheel group
What I Learned (the hard way)
Adding someone to the wheel group is like giving them the “admin lightsaber.” Use responsibly.
visudo saves lives (and jobs).
Sudo abuse is real—and totally traceable. Your logs will snitch.
Tomorrow’s Challenge Teaser
Tomorrow we take a peek into the hidden world of groups. Primary, secondary, and why “newdev” is in six of them.
Want to follow along?
Post your commands, share your fails, and tag your fellow sudo warriors.
Top comments (0)