Q: Standard Unix permissions (owner/group/other) are insufficient for your use case. You need one specific user to have read access to a file without changing the file's owner or group. How do you accomplish this?
POSIX ACLs (Access Control Lists) extend the traditional owner/group/other permission model by allowing per-user and per-group rules on files and directories.
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: POSIX Access Control Lists (ACLs), fine-grained permissions.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
POSIX ACLs (Access Control Lists) extend the traditional owner/group/other permission model by allowing per-user and per-group rules on files and directories.
- Set ACL:
setfacl -m u:username:rwx file - Set default ACL (inherited by new files):
setfacl -d -m u:alice:rx /var/data/ - Remove ACL:
setfacl -x u:alice file
Remediation & Permanent Safeguards
To grant a specific user read access: To verify: Output: Key commands: Note: The filesystem must be mounted with ACL support (most modern ext4/XFS filesystems enable this by default). A + symbol appears in ls -l output when ACLs are set (e.g., -rw-r--r--+).
setfacl -m u:alice:r /var/data/report.csv
- Remove all ACLs:
setfacl -b file
- Set ACL: setfacl -m u:username:rwx file
- Set default ACL (inherited by new files): setfacl -d -m u:alice:rx /var/data/
- Remove ACL: setfacl -x u:alice file
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 Standard Unix permissions 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 Standard Unix permissions
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 Standard Unix permissions 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 Standard Unix permissions
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).