Writing setuid or setgid Scripts in bash

You have a problem you think you can solve by using the setuid or setgid bit on a shell script.

Use Unix groups and file permissions and/or sudo to grant the appropriate users the least privilege they need to accomplish their task.
Using the setuid or setgid bit on a shell script will create more problems—especially security problems—than it solves.

Some systems (such as Linux) don’t even honor the setuid bit on shell scripts, so creating setuid shell scripts creates an unnecessary portability problem in addition to the security risks.

setuid root scripts are especially dangerous, so don’t even think about it.

Use sudo. setuid and setgid have a different meaning when applied to directories than they do
when applied to executable files.

When one of these is set on a directory it causes any newly created files or subdirectories to be owned by the directory’s owner or group, respectively.

Note you can check a file to see if it is setuid by using test -u or setgid by using test -g.