Q: What is the difference between running `su root` and `su - root`?
su root switches your UID privileges to root, but it explicitly preserves your existing user's environment. You keep your old $PATH, current working directory, and aliased commands.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "During an on-call shift, our alerts triggered when a critical Linux production server exhibited this behavior. The interviewer is testing: Linux environments, login shells.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
su rootswitches your UID privileges to root, but it explicitly preserves your existing user's environment. You keep your old$PATH, current working directory, and aliased commands.su - root(with the hyphen) forces a full login shell. It completely purges your previous environment, resets environment variables, changes the directory to/root, and sources root's.bash_profile. This is the vastly safer and preferred method, ensuring you aren't accidentally executing harmful bin paths inherited from the unprivileged user.
Remediation & Permanent Safeguards
Execute the resolution runbook and verify workload health:
- su root switches your UID privileges to root, but it explicitly preserves your existing user's en...
- su - root (with the hyphen) forces a full login shell. It completely purges your previous environ...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring difference running root SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring difference running root
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring difference running root Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring difference running root
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).