Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Is there any cmd to kill a process including its childs ( or sub processes spawned by
Top Forums Shell Programming and Scripting Is there any cmd to kill a process including its childs ( or sub processes spawned by Post 93897 by gvsreddy_539 on Friday 23rd of December 2005 04:01:34 AM
Old 12-23-2005
Vino,
Thx for the quick reply.
pstree lists all the pids of sub processes with pnames.

anyhow,we need 2 again manually pick-up those pids and kill.right?

after pstree...we can procees that list usoing any of the utilities and pick only the pids and pipe the 2 xargs.

I think this way ll b fine..right?

or pls suggest me if there is a better way.

Thanks,
Venkat (BEA Systems).
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to use Kill cmd when detect rogue

I'm system administrator and most of our Unix servers in the company host database that are accessed frequently by company employees. One day, one particular Unix server has been reported as being very slow. Upon further investigation using the ps command, we've found a rogue process that is... (8 Replies)
Discussion started by: agui
8 Replies

2. UNIX for Advanced & Expert Users

When kill doesnt work, how to kill a process ?

Hi All, I am unable to kill a process using kill command. I am using HP-UX system. I have tried with kill -9 and i have root privilages. How can i terminate this daemon ? ? ? Regards, Vijay Hegde (3 Replies)
Discussion started by: VijayHegde
3 Replies

3. Shell Programming and Scripting

How to kill a process and its childs given pid and userid

I need to write a shell script which would take 2 arguments pid , userid. Then it should kill all the child process under it. If a child process is not killed then it should wait for 1 minute and should kill. can anybody give me the idea to write it? (0 Replies)
Discussion started by: nani_g
0 Replies

4. Linux

How to receive results from processes spawned on external machines using SSH

I am trying to get the number of cpus on a farm of linux boxes (about 100 of them) by 'sshing' to each of them and checking their /proc/cpuinfo file. So I have a local script localscript.sh on each of those 100 machines which retrieves the number of cpus in it by using its /proc/cpuinfo file.... (1 Reply)
Discussion started by: waavman
1 Replies

5. UNIX for Dummies Questions & Answers

kill/pkill process by CMD info.

I have a process that I'd like to kill. Doing a "ps -fu myusername" gives me: UID PID PPID C STIME TTY TIME CMD myusername 5443 1 0 10:05 ? 00:00:00 /bin/sh /some/path/crap.sh -s /yet/another/path/parentProcess myusername 5593 5443 0 ... (2 Replies)
Discussion started by: mrwatkin
2 Replies

6. UNIX for Dummies Questions & Answers

Finding apache process id that is spawned by a wget

Hi, I have a situation where I am writing a programme that runs a series of long running PHP scripts that can take anything from 20 minutes to 10 hours to execute. I have a solution half implemented where I use via php exec(wget <location to command>) and get the process id back. This... (1 Reply)
Discussion started by: mrploddy
1 Replies

7. Shell Programming and Scripting

Suppressing output of a spawned telnet process

Hi, I'm trying to spawn a telnet process and trying to do some actions in the remote host using expect script. I would like to know how to suppress all the output in order the user using the script should not be able to see any actions done on the remote host. I tried using the "log_user 0"... (8 Replies)
Discussion started by: arun_maffy
8 Replies

8. Shell Programming and Scripting

Preparing a list of spawned processes

Hi All I'm currently trying to develop a script which will find the child processes of a process ID already passed to the script. I then need the script to look for spawned processes of these child processes and so on until it can't find any more. For example At the moment, I have to... (6 Replies)
Discussion started by: huskie69
6 Replies

9. Shell Programming and Scripting

Process behavior different when spawned from single terminal

So this one just plain confuses me. I have a bunch of somewhat CPU intensive processes that all communicate using a shared memory region. Some of these programs are threaded and some also change the scheduling to FIFO or round robin. The good news is that everything works as long as I spawn... (3 Replies)
Discussion started by: talkingfennel
3 Replies

10. Shell Programming and Scripting

Kill an specific process ID using the KILL and GREP commands

Good afternoon I need to KILL a process in a single command sentence, for example: kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'` That sentence Kills the process ID corresponding to the program CAL255.4ge. However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies

LEARN ABOUT OSX

kill

KILL(1) 						    BSD General Commands Manual 						   KILL(1)

NAME

     kill -- terminate or signal a process

SYNOPSIS

     kill [-s signal_name] pid ...
     kill -l [exit_status]
     kill -signal_name pid ...
     kill -signal_number pid ...

DESCRIPTION

     The kill utility sends a signal to the processes specified by the pid operand(s).

     Only the super-user may send signals to other users' processes.

     The options are as follows:

     -s signal_name
	     A symbolic signal name specifying the signal to be sent instead of the default TERM.

     -l [exit_status]
	     If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status.

     -signal_name
	     A symbolic signal name specifying the signal to be sent instead of the default TERM.

     -signal_number
	     A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.

     The following pids have special meanings:
     -1      If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.

     Some of the more commonly used signals:
     1	     HUP (hang up)
     2	     INT (interrupt)
     3	     QUIT (quit)
     6	     ABRT (abort)
     9	     KILL (non-catchable, non-ignorable kill)
     14      ALRM (alarm clock)
     15      TERM (software termination signal)

     Some shells may provide a builtin kill command which is similar or identical to this utility.  Consult the builtin(1) manual page.

SEE ALSO

     builtin(1), csh(1), killall(1), ps(1), kill(2), sigaction(2)

STANDARDS

     The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.

HISTORY

     A kill command appeared in Version 6 AT&T UNIX.

BUGS

     A replacement for the command ``kill 0'' for csh(1) users should be provided.

BSD
								  April 28, 1995							       BSD
All times are GMT -4. The time now is 11:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy