Sponsored Content
Top Forums Shell Programming and Scripting Kill all proceess with the name XXX Post 302763013 by fpmurphy on Tuesday 29th of January 2013 10:58:49 AM
Old 01-29-2013
Have a look at the pkill manpage.
 

8 More Discussions You Might Find Interesting

1. 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

2. Shell Programming and Scripting

Delete a file from XXX.tar.Z

Hi All can u please let me know how to delete a file from XXX.tar.Z file with out uncompressing this file. thanks in advance. --Bali (0 Replies)
Discussion started by: balireddy_77
0 Replies

3. UNIX for Dummies Questions & Answers

xxx.tar.gz error

Hi All, We have taken data backup using gzip but when we try to restore from ex:xxx.tar.gz file got below error. invalid compressed data--crc error and invalid compressed data--length error How to recover my original data. Thanks in advance for your suggestion (1 Reply)
Discussion started by: bache_gowda
1 Replies

4. UNIX for Dummies Questions & Answers

grep XXX that not followed by YYY

I want to grep all lines containing blocking sess= that are not followed by 0x0 cat trace.log blocking sess=0x0 blocking sess=0x0 rrrr...... blocking sess=121 blocking sess=0x0 blocking sess=0x0 blocking sess=0x0 some other lines blocking sess=001 blocking sess=0x0 blocking sess=0x1... (6 Replies)
Discussion started by: ynixon
6 Replies

5. AIX

echo $varibla | mail -s "subject" "xxx@xxx.com" not ruuning as expected

Hi Folks, As per the subject, the following command is not working as expected. echo $variable | mail -s "subject" "xxx@xxx.com" Could anyone figure it out whats wrong with this. I am using AIX box. Regards, (2 Replies)
Discussion started by: gjarms
2 Replies

6. 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

7. Shell Programming and Scripting

Extracting entries starting with xxx

Hello, I am trying to extract all words (entries) from a file beginning with 123. For example: ververv ewfaafa 123asd 4334j fdgfgf fdfdssd 123890 xxxxx eeee sss 1234 sdfsf were sfs fbdsdfb fsdg sdgfsd bfg sdfb dsfb sdfg sdf ergerg 123pop sdfgdfg 123ww 123qq dffg Desired output: 123asd... (4 Replies)
Discussion started by: palex
4 Replies

8. Red Hat

Gnome3 locksup on new Linux kernel 12.6.xxx & 12.5.xxx

Hi Forum Ive been having a problem with the kernal(s) for some strange reason it every time I try and access the date and time/calendar or system settings it locks up the whole laptop and nothing responds. :(. This doesn't happen 11.10.xxx kernel . Any help would be much appreciated and thank you... (1 Reply)
Discussion started by: ShinTec
1 Replies
KILL(1) 						      General Commands Manual							   KILL(1)

NAME
kill - terminate a process with extreme prejudice SYNOPSIS
kill [ -sig ] processid ... kill -l DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu- ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in /usr/include/signal.h, stripped of the common SIG prefix. The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special meanings; see kill(2) for details. The killed processes must belong to the current user unless he is the super-user. The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1). Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill arguments. See csh(1) for details. SEE ALSO
csh(1), ps(1), kill(2), sigvec(2) BUGS
A replacement for ``kill 0'' for csh(1) users should be provided. 4th Berkeley Distribution April 20, 1986 KILL(1)
All times are GMT -4. The time now is 09:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy