You set the setuid bit on a script using chmod u+s script.sh, but it doesn't run with owner permissions. What is the likely problem?

medium📝 Debug Q14 of 15

Linux CLI - File Permissions and Ownership

You set the setuid bit on a script using chmod u+s script.sh, but it doesn't run with owner permissions. What is the likely problem?

AYou need to set the sticky bit instead

BThe file owner must be root for setuid to work

CThe script is a shell script and setuid does not work on scripts

DYou forgot to set execute permission

Step-by-Step Solution

Solution:

Step 1: Understand setuid behavior on scripts
Most Linux systems ignore setuid on shell scripts for security reasons.
Step 2: Evaluate other options
Sticky bit is unrelated, owner need not be root, and execute permission is usually set if script runs.
Final Answer:
The script is a shell script and setuid does not work on scripts -> Option C
Quick Check:
Setuid ignored on scripts [OK]

Quick Trick: Setuid rarely works on scripts, only on binaries [OK]

Common Mistakes:

Master "File Permissions and Ownership" in Linux CLI

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Linux CLI Quizzes