Linux Survival Basics
Read-only, sensitive outputList Effective sudo Privileges
You need to see what sudo allows for the current user.
Command
sudo -lBefore you run this
System impact: Read-only. Output may expose users, paths, tokens, keys, IPs, process arguments, or log details.
When not to use it: Do not paste sudo output publicly without redacting hostnames and command paths.
Expected output
Allowed or denied sudo commands for the current account, after authentication if required.
System impact
Read-only, sensitive output. Nothing changes. The command reads current state and prints diagnostic evidence.
May require elevated permissions on protected paths or service-owned files.
Recovery / rollback: no state is changed.
When to use it
Use before editing sudoers rules.
When not to use it
Do not paste sudo output publicly without redacting hostnames and command paths.
Example run
Commands shown
These are the commands shown for inspection. Treat them as an example, not proof that your system will behave identically.
sudo -lsudo -l
next steps
Related commands
List sudo Group Members
Before granting sudo, see who already has it.
getent group sudo
Find the dpkg Lock Owner
Find the process holding the dpkg lock before touching lock files.
sudo lsof /var/lib/dpkg/lock-frontend /var/lib/dpkg/lock 2>/dev/null
Inspect One Process Open Files
Look at one target process, not the whole host, when pressure is scoped.
sudo lsof -p 1234 | head
Count Open Files for One Process
Count handles for the target process before raising limits.
sudo lsof -p 1234 | wc -l
Show User Groups
Group membership explains many sudo and access failures.
groups username
next diagnostic step
Where to go from this command
- User not in sudoers hub Use before sudoers edits.
Study mapping
Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.
Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.