01-29-2013
First of all you can easily get pids with pgrep command which does the same thing like your code and you can even use pkill which kills running processes by their names on similar basis. You just have to be very cautious about what pattern you are killing processes with.
Second thing is that you can even use loops within one line simply by separating different lines with semi-colons.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there a command in HP Unix which can be used inside a K shell to find out the maximum number of processes (PIDs) a pc can generate?
Any help will be greatly appreciated.
Steve (8 Replies)
Discussion started by: stevefox
8 Replies
2. Shell Programming and Scripting
I am trying to write a Shell script wherein the shell needs to read a list of PID in the File $stat/bin/Process and compare it to the PID of the processes running on a server.
Also the script should return KO(not OK) with corresponding label :-
a) When an environmental variable not... (2 Replies)
Discussion started by: marconi
2 Replies
3. Shell Programming and Scripting
Hi,
There is a file having a list of running PIDs and another file having a list of registered PIDs. How can we check if the number of running PIDs are less or more than the registered PIDs, comparing the total no. in each and also each value.
Request you to pls give your inputs.
Thanks a... (2 Replies)
Discussion started by: marconi
2 Replies
4. Shell Programming and Scripting
Hi,
There is a file having a list of running PIDs (pid_process) and another file having a list of registered PIDs (pid_regieter).
I want to check if:-
a) there is at least one running PID that does not correspond to a
registered PID (listing the PID not registered in the file)
... (1 Reply)
Discussion started by: marconi
1 Replies
5. Shell Programming and Scripting
I have a script that conducts some SSH calls and I would like to capture the child info so that I can do a sleep and then a cleanup to make sure they do not stay out there as ghosts.
I was told I could do something like this...
#!/bin/sh
for m = job1, job2, job3
x=1... (4 Replies)
Discussion started by: LRoberts
4 Replies
6. Solaris
I am trying to determine the root cause of a java process that dies trying to startup during it's cron job.
I did go ahead and change the time that it starts up in the cron file and now it starts successfully.
However is there a way to determine what PID a process was attempting to get when... (5 Replies)
Discussion started by: vedder191
5 Replies
7. Shell Programming and Scripting
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
8. Proxy Server
Details Samba server:
Release: 5.10
Kernel architecture: sun4u
Application architecture: sparc
Hardware provider: Sun_Microsystems
Kernel version: SunOS 5.10 Generic_142909-17
Samba version:
Samba version 3.5.6
Smb.conf file section Global:
# smb.conf for Airbus Industries fuer... (0 Replies)
Discussion started by: Jean-Guillaume
0 Replies
9. Shell Programming and Scripting
im looking for a portable way to get the PID of the script that is running, and to get every other PIDs that are spawned from it.
and by ever other PIDs, i presume, that would be "child processes".
however, i want to shy away from using any command that is not available on every single unix... (1 Reply)
Discussion started by: SkySmart
1 Replies
10. UNIX for Beginners Questions & Answers
First of all, I'd like to congratulate this big family and all members for all the work you do!
I'm trying to do an script or sentence which kills an specific printers PIDs: all printers PIDs older than 72h running in the server.
Steps:
1.- List all printers PID sorting by date:
ps... (6 Replies)
Discussion started by: djflu
6 Replies
PGREP(1) Linux User's Manual PGREP(1)
NAME
pgrep, pkill - look up or signal processes based on name and other attributes
SYNOPSIS
pgrep [-flnvx] [-d delimiter] [-P ppid,...] [-g pgrp,...]
[-s sid,...] [-u euid,...] [-U uid,...] [-G gid,...]
[-t term,...] [pattern]
pkill [-signal] [-fnvx] [-P ppid,...] [-g pgrp,...]
[-s sid,...] [-u euid,...] [-U uid,...] [-G gid,...]
[-t term,...] [pattern]
DESCRIPTION
pgrep looks through the currently running processes and lists the process IDs which matches the selection criteria to stdout. All the cri-
teria have to match. For example,
pgrep -u root sshd
will only list the processes called sshd AND owned by root. On the other hand,
pgrep -u root,daemon
will list the processes owned by root OR daemon.
pkill will send the specified signal (by default SIGTERM) to each process instead of listing them on stdout.
OPTIONS
-d delimiter
Sets the string used to delimit each process ID in the output (by default a newline). (pgrep only.)
-f The pattern is normally only matched against the process name. When -f is set, the full command line is used.
-g pgrp,...
Only match processes in the process group IDs listed. Process group 0 is translated into pgrep's or pkill's own process group.
-G gid,...
Only match processes whose real group ID is listed. Either the numerical or symbolical value may be used.
-l List the process name as well as the process ID. (pgrep only.)
-n Select only the newest (most recently started) of the matching processes.
-P ppid,...
Only match processes whose parent process ID is listed.
-s sid,...
Only match processes whose process session ID is listed. Session ID 0 is translated into pgrep's or pkill's own session ID.
-t term,...
Only match processes whose controlling terminal is listed. The terminal name should be specified without the "/dev/" prefix.
-u euid,...
Only match processes whose effective user ID is listed. Either the numerical or symbolical value may be used.
-U uid,...
Only match processes whose real user ID is listed. Either the numerical or symbolical value may be used.
-v Negates the matching.
-x Only match processes whose name (or command line if -f is specified) exactly match the pattern.
-signal
Defines the signal to send to each matched process. Either the numeric or the symbolic signal name can be used. (pkill only.)
OPERANDS
pattern
Specifies an Extended Regular Expression for matching against the process names or command lines.
EXAMPLES
Example 1: Find the process ID of the named daemon:
unix$ pgrep -u root named
Example 2: Make syslog reread its configuration file:
unix$ pkill -HUP syslogd
Example 3: Give detailed information on all xterm processes:
unix$ ps -fp $(pgrep -d, -x xterm)
Example 4: Make all netscape processes run nicer:
unix$ renice +4 `pgrep netscape`
EXIT STATUS
0 One or more processes matched the criteria.
1 No processes matched.
2 Syntax error in the command line.
3 Fatal error: out of memory etc.
NOTES
The process name used for matching is limited to the 15 characters present in the output of /proc/pid/stat. Use the -f option to match
against the complete command line, /proc/pid/cmdline.
The running pgrep or pkill process will never report itself as a match.
BUGS
The options -n and -v can not be combined. Let me know if you need to do this.
Defunct processes are reported.
SEE ALSO
ps(1) proc(5) regex(5)
STANDARDS
pkill and pgrep were introduced in Sun's Solaris 7. This implementation is fully compatible.
AUTHOR
Kjetil Torgrim Homme <kjetilho@ifi.uio.no>
Michael K. Johnson <johnsonm@redhat.com> is the current maintainer of the procps package.
Please send bug reports to <procps-list@redhat.com>
Linux June 25, 2000 PGREP(1)