Sponsored Content
Operating Systems AIX Kill multiple processes ran by root Post 303005640 by jeffs42885 on Friday 20th of October 2017 01:55:50 PM
Old 10-20-2017
Quote:
Originally Posted by rbatte1
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
Client as in my company. Who is running the daemon as non root when its not really needed. I've seen several implementations of this product but never seen the daemon running as root.

Heres my end result-

Code:
ps -ef | grep [p]rogram | awk '{print $2}' | xargs sudo kill

 

10 More Discussions You Might Find Interesting

1. Programming

C program to kill root processes

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

Ran out of space on /dev/root partition

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

kill all processes

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

Kill several processes at a time

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

kill processes

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

kill the processes seen under ptree

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

Kill processes

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

kill all user processes

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

kill multiple processes by name

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

find the no of processes that ran 2 hours before or earlier

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
svnserve(8)						      System Manager's Manual						       svnserve(8)

NAME
svnserve - Server for the 'svn' repository access method SYNOPSIS
svnserve [options] DESCRIPTION
svnserve allows access to Subversion repositories using the svn network protocol. It can both run as a standalone server process, or it can run out of inetd. You must choose a mode of operation when you start svnserve. The following options are recognized: -d, --daemon Causes svnserve to run in daemon mode. svnserve backgrounds itself and accepts and serves TCP/IP connections on the svn port (3690, by default). --listen-port=port Causes svnserve to listen on port when run in daemon mode. --listen-host=host Causes svnserve to listen on the interface specified by host, which may be either a hostname or an IP address. --foreground When used together with -d, this option causes svnserve to stay in the foreground. This option is mainly useful for debugging. -i, --inetd Causes svnserve to use the stdin/stdout file descriptors, as is appropriate for a daemon running out of inetd. -h, --help Displays a usage summary and exits. -r root, --root=root Sets the virtual root for repositories served by svnserve. The pathname in URLs provided by the client will be interpreted relative to this root, and will not be allowed to escape this root. -R --read-only Force all write operations through this svnserve instance to be forbidden, overriding all other access policy configuration. Do not use this option to set general repository access policy - that is what the conf/svnserve.conf repository configuration file is for. This option should be used only to restrict access via a certain method of invoking svnserve - for example, to allow write access via SSH, but not via a svnserve daemon, or to create a restricted SSH key which is only capable of read access. -t, --tunnel Causes svnserve to run in tunnel mode, which is just like the inetd mode of operation (serve one connection over stdin/stdout) except that the connection is considered to be pre-authenticated with the username of the current uid. This flag is selected by the client when running over a tunnel agent. --tunnel-user=username When combined with --tunnel, overrides the pre-authenticated username with the supplied username. This is useful in combination with the ssh authorized_key file's "command" directive to allow a single system account to be used by multiple committers, each having a distinct ssh identity. -T, --threads When running in daemon mode, causes svnserve to spawn a thread instead of a process for each connection. The svnserve process still backgrounds itself at startup time. -X, --listen-once Causes svnserve to accept one connection on the svn port, serve it, and exit. This option is mainly useful for debugging. Once the client has selected a repository by transmitting its URL, svnserve reads a file named conf/svnserve.conf in the repository direc- tory to determine repository-specific settings such as what authentication database to use and what authorization policies to apply. See the svnserve.conf(5) man page for details of that file format. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +--------------------+-----------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +--------------------+-----------------+ |Availability | SUNWsvn | +--------------------+-----------------+ |Interface Stability | Committed | +--------------------+-----------------+ NOTES
Source for Subversion is available on http://opensolaris.org. svnserve(8)
All times are GMT -4. The time now is 06:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy