Q: A junior admin removed the executable bit from the `chmod` command itself (`chmod -x /bin/chmod`). How do you fix this since you can't use chmod to fix chmod?
Since /bin/chmod is essentially just an ELF binary, you can invoke the dynamic linker directly to execute the file without it needing the execute bit. The dynamic linker/loader itself is executable.
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: "In an interview, I explain my systematic Linux troubleshooting methodology using Brendan Gregg's USE method. The interviewer is testing: Deep understanding of Linux dynamic linking and program execution.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
Since /bin/chmod is essentially just an ELF binary, you can invoke the dynamic linker directly to execute the file without it needing the execute bit. The dynamic linker/loader itself is executable. /lib64/ld-linux-x86-64.so.2 /bin/chmod +x /bin/chmod (path varies by distro). Alternatively, you could use a language interpreter built into the system that already has execute permissions: Python: python -c "import os; os.chmod('/bin/chmod', 0o755)" Or simply copy a tool that can set attributes: cp /bin/ls /tmp/ls; cat /bin/chmod > /tmp/ls (Wait, this is complex). The dynamic linker or Python approach is the cleanest SRE-level answer.
- Immediate Triage: Since /bin/chmod is essentially just an ELF binary, you can invoke the dynamic linker directly
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
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 junior admin removed 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 junior admin removed
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 junior admin removed 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 junior admin removed
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).