Echo/kill pgrep Post: 303024499

10 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

2. Programming

kill(0,-9) don't kill the process

Hi all i have simple c program , when i wish to kill the app im using kill(0,-9) , but it seams this command don't do any thing and the program. just ignore it . what im doing wrong here ? im using HP-UX ia64 Thanks

3. AIX

pgrep substitute for porting a linux script to AIX 5.x

Hi, I'm trying to get this script to work on an AIX 5.3 box, I couldn't get pgrep for AIX, I also realize that ps works differently on the IBM boxes. Could anybody just give me the specifics of a work around for my problem, I'll adjust the whole script: #!/bin/bash # applabs.com #to do: #...

4. Programming

pgrep returns 256

Hi Everyone, I have a strange behaviour In my c program i use this line: int retval = system("pgrep encoder"); while i expect retval to contain 0,1,2,3 i get 256. did i do something wrong? thanks, Alex

5. UNIX for Dummies Questions & Answers

PGREP Arguments

I'm trying to figure out how to use pgrep to pull the arguments of a process. Given: root 308 1 0 00:00 ? 00:00:00 /bin/sh /some/random/path/somescript.sh -flag /another/path/blahI can get the pid (308) using this command: pgrep shHowever, what if I wanted to pull by "somescript.sh"...

6. HP-UX

pgrep doesn't perform full command line pattern matching

Hi! I need to get PID of some particular process and I wonder if I can use pgrep tool for this purpose. The problem is that pgrep doesn't perform pattern matching on the whole command line, even if I use -f key. Parsing output of ps command is not quite convenient... Also deamon, which PID I need...

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

8. Shell Programming and Scripting

Ssh and pgrep not working

I have setup SSH keys . Trying to grep to get PID of remote jvm's . this is what am doing ssh -q testuser1@myhost.com 'PID1=pgrep -fl testapp1|awk "{print $1}";PID2=pgrep -fl testapp2|awk "{print $1}" ' echo $PID1, $PID2 it throws error"sh: -fl: command not found" ---------- Post updated...

9. Shell Programming and Scripting

Pgrep for processes which are not associated with a terminal in Ubuntu

I would like to find all of the PIDs of processes which are not associated with a terminal and started by CRON. When I do the ps aux | less command, I see in the TTY field a lot of processes with ? character I would like to get those processes ID, is there a way to do that with pgrep? ...

10. Shell Programming and Scripting

Pgrep not showing desired output

I am searching for a process that should be up and running. Im using the following command ps -ef | grep elasticsearch to get elastic+ 1673 1 0 Jan29 ? 05:08:56 /bin/java -Xms4g -Xmx4g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC...

LEARN ABOUT REDHAT

kill

KILL(1) 						     Linux Programmer's Manual							   KILL(1)

NAME

       kill - terminate a process

SYNOPSIS

       kill [ -s signal | -p ] [ -a ] [ -- ] pid ...
       kill -l [ signal ]

DESCRIPTION

       The command kill sends the specified signal to the specified process or process group.  If no signal is specified, the TERM signal is sent.
       The TERM signal will kill processes which do not catch this signal.  For other processes, it may be necessary to use the KILL  (9)  signal,
       since this signal cannot be caught.

       Most  modern  shells  have  a  builtin  kill function, with a usage rather similar to that of the command described here. The `-a' and `-p'
       options, and the possibility to specify pids by command name is a local extension.

OPTIONS

       pid... Specify the list of processes that kill should signal.  Each pid can be one of five things:

	      n      where n is larger than 0.	The process with pid n will be signaled.

	      0      All processes in the current process group are signaled.

	      -1     All processes with pid larger than 1 will be signaled.

	      -n     where n is larger than 1.	All processes in process group n are signaled.	When an argument of the form `-n' is given, and it
		     is  meant	to  denote  a process group, either the signal must be specified first, or the argument must be preceded by a `--'
		     option, otherwise it will be taken as the signal to send.

	      commandname
		     All processes invoked using that name will be signaled.

       -s signal
	      Specify the signal to send.  The signal may be given as a signal name or number.

       -l     Print a list of signal names.  These are found in /usr/include/linux/signal.h

       -a     Do not restrict the commandname-to-pid conversion to processes with the same uid as the present process.

       -p     Specify that kill should only print the process id (pid) of the named processes, and not send any signals.

SEE ALSO

       bash(1), tcsh(1), kill(2), sigvec(2), signal(7)

AUTHOR

       Taken from BSD 4.4.  The ability to translate process names to process ids was added by Salvatore Valente <svalente@mit.edu>.

Linux Utilities 						  14 October 1994							   KILL(1)

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

When kill doesnt work, how to kill a process ?

Discussion started by: VijayHegde

2. Programming

kill(0,-9) don't kill the process

Discussion started by: umen

3. AIX

pgrep substitute for porting a linux script to AIX 5.x

Discussion started by: thebytegrill

4. Programming

pgrep returns 256

Discussion started by: alex889