Using the chmod +s file permission.

[maheshs]

We are a group of developers and we start some background daemon processes.

We have our own logins and we need to write a shell script that would start and stop (kill )these background processes irrespective of the person who started these processes.

We are not able to kill the processes started by the other developer thru our userid's.

The chmod +s command too is not working for the shell script that we have written.

Please advice.

Mahesh.

 

[vgersh99]

who owns the script? [chown]

vlad
+----------------------------+
| #include<disclaimer.h> |
+----------------------------+

 

[Clairvoyant1332]

The shell script needs to be owned by root with permissions 4755. The first line of the script should also look like this in order for it to run setuid (assuming you're using Bourne shell):

#!/bin/sh -p

Dennis

 

[usige]

Make sure your version of Unix supports setuid on shell scripts. Certain version will ignore setuid if it sees a #! line.

 

[maheshs]

Sorry guys I hven'r tried any of your suggestions as I am sick :-(.

vlad:
The script is owned by the person who wrote it.
It has execute pemissions and anyone can fire it.

The processes started by the script now belong to the person who started it and other developers are not able to kill the processes as and when they like.

Thanks.

msankpal.

 

[tarn]

You could always install and setup SUDO and configure it so the developer group has (sudo)root permisions to stop that &quot;and only&quot; that application/script as root?

Good Luck'
Laurie

 

[Annihilannic]

I would suggest you create a new user in the same group as the rest of the developers specifically for running these daemon processes. Then either use sudo or simply su - theuser -c &quot;/path/to/startup/script&quot;, for example. These would be safer than having setuid shell scripts.


Annihilannic.