10-20-2017
By 'client', do you mean the person/company paying you or client software?
If it's the former, tell them that they will not be supported, or perhaps get them to run the stop script as root.
If it is client software, then presumably somewhere there is a root-owned & SUID executable somewhere that is called in the start-up. Find that and take away the SUID.
Does that get you any closer?
Robin
10 More Discussions You Might Find Interesting
1. Programming
Hello,
First let me start by saying I have searched the forum and read all the SUID stuff but it is not in the neighborhood I am looking for.
Here is the problem. We want to grant a non super-user permission to kill root processes but only if the process matches certain criteria. ... (8 Replies)
Discussion started by: TioTony
8 Replies
2. Filesystems, Disks and Memory
hi,
I have a SCO unix server which has a 36gb hard drive, but the IT company who supplied it assigned 1gb to /dev/root, 15mb to /dev/boot and 33gb to /dev/u.
The /dev/root partition is now full, is there a way I can use the 33gb assigned to /dev/u without loosing any data, preferably... (2 Replies)
Discussion started by: Martyn
2 Replies
3. Shell Programming and Scripting
i have a very short file that has in it a line for a find command.
now, when i run this script and I kill the script later, using the ps -ef | grep scriptname. i noticed kill -9 kills the script itself but does not kill the internal find command that it gave birth to.
say theres a file... (0 Replies)
Discussion started by: Terrible
0 Replies
4. UNIX for Dummies Questions & Answers
Hello,
ps -C a*
returns the list of the process I need to kill.
but
ps -C a* -o pid | kill
does not work and I can't get the syntax right.
Thanks for any help (4 Replies)
Discussion started by: JCR
4 Replies
5. Solaris
how to kill the processes of aperticular user?
because i have nearly 25000 process are there for perticular user. i need to kill.
Please provide the information?
Regards,
Rajesh (3 Replies)
Discussion started by: pmrajesh21
3 Replies
6. Solaris
Hi,
How to kill the processes running under ptree ?
I am noticing lot of processes running under ptree with ssh ? I tried to kill with -9 option which is not working ?
Thanks,
Radhika. (2 Replies)
Discussion started by: radhirk
2 Replies
7. Shell Programming and Scripting
for i in 'ps -f | grep textedit'
do
kill $i
done
I wrote this but it wont work.
I am trying to find processes and kill them.
Any help would be welcome. (1 Reply)
Discussion started by: hawaiifiver
1 Replies
8. Shell Programming and Scripting
Hi there, i've been searching all over and i thought i had understood the way i should go to kill all the processes related to a user. But i'm getting more confused then i was.
By lunch time i have to make a database backup, and for that all the users shoul logout. The problem is that many users... (4 Replies)
Discussion started by: vascobrito
4 Replies
9. Shell Programming and Scripting
Want to kill multiple processes by name. for the example below, I want to kill all 'proxy-stagerd_copy' processes.
I tried this but didn't work:
>> ps -ef|grep proxy_copy
root 991 986 0 14:45:34 ? 0:04 proxy-stagerd
root 1003 991 0 14:45:49 ? 0:01... (2 Replies)
Discussion started by: catalinawinemxr
2 Replies
10. UNIX for Dummies Questions & Answers
Is there a way to find out the total no of processes that were running ?
- 2 or 3 hours before
- list those no of processes (3 Replies)
Discussion started by: jansat
3 Replies
info(4) Kernel Interfaces Manual info(4)
NAME
info - diskless client configuration information file
DESCRIPTION
The file is a POSIX shell sourceable file which contains parameter definitions used at boot time. Typically, it will be an empty file and
default values will be used for all parameters. Following is the list of parameters which can be defined in the file:
Specifies the IP address of the client's private root server. If this is not
specified, the client's private root server defaults to the boot server.
Specifies the pathname to the client's private root on the private root
server. If this is not specified, the client's private root path defaults to
Specifies the NFS mount options to mount the client's private root from
the private root server. If this is not specified, the mount options default to
Specifies the NFS mount options to mount the client's
directory from the boot server. If this is not specified, the mount options default to
Specifies whether NFS should be configured as primary swap. (NOTE: In
order to swap to NFS, a diskless kernel must be configured with tunable parameter set to 1.) If a diskless
machine has a local swap disk and swap to NFS is not desired, the parameter should be set to the value of 1
and the diskless kernel should be configured without setting to 1. If this parameter is not specified in
the file and the kernel tunable parameter is set to 1, then NFS will be configured as primary swap.
If not set, this parameter defaults to a value of 1, and results in the
removal of all swapfiles above the configured swap minimum (swap is specified in the client's when a disk-
less client boots. This ensures that extraneous swapfiles at boot time are removed, thus freeing disk
space. If is set to 0 in the file, removal of extra swapfiles is disabled. This may result in faster boot
times due to the time savings in creating additional swap files.
The file resides in the same directory as the client's kernel () on the boot server and is retrieved at boot time using command. By
default, when a diskless client is created, an empty file is placed in the client's kernel directory. This ensures that all parameters
revert to their default values (see above). If the file is not present, this is an error.
EXAMPLES
An example file is shown below:
FILES
info(4)