If the loop goes over the running processes, how are the not running processes detected then?
The following loops over the files to get the DB instances, then looks them up in the ps output:
It avoids bash4 arrays - instead it does a lookup in a simple variable.
Last edited by MadeInGermany; 11-16-2018 at 01:17 PM..
This User Gave Thanks to MadeInGermany For This Post:
Hi,
Am supposed to use message queues to send and receive messages between the processes. when i was working on that i realised that the message qid and the message queue related data should be maintained in a shared memory so that it can be accessed by all the processes. Could anybody refer... (10 Replies)
I am trying to write a script that will help me put a file into excel with little manipulation. Below is a sample of the file im using.
Group1:*:gid1:user,user
Group2:*:gid2:user,user
Group3:*:gid3:user,user,user,user,user,user,user
Group4:*:gid4:user,user
I marked in red the part that is... (1 Reply)
Hello all, I have been asked to exercise my shell scripting and it has been 10 plus years since I used to do it so I can not remember hardly anything and ask for your help.
What I need to do is copy a line out of a file that can be 10 to 100 characters long, I then need to parse this line into... (3 Replies)
I have a file with data records separated by multiple equals signs, as below.
==========
RECORD 1
==========
RECORD 2
DATA LINE
==========
RECORD 3
==========
RECORD 4
DATA LINE
==========
RECORD 5
DATA LINE
==========
I need to filter out all data from this file where the... (2 Replies)
i have to remove the commented (/* . . . .*/) part which starts in one line and ends in other.help me with generic code because i have 1000 to 10k lines code which i have to remove.
data one;
set work.temp;
input name age;
infile filename;
/* dfsdf
dsfs
sdfdf
dsdd
sdfsf
sdfsf
sfs... (4 Replies)
It looks like if matching and deleting the last line confuses 'sed' so it does not recognize '$' address. Consider:
sed -e '/^3/d' -e '$ a text'
supposed to delete a line starting with '3' and then append 'text' after the last line of input. But, if it is the last line of input which starts... (2 Replies)
Hello,
Currently, I am reading few queries from the below .sql file
--SOURCE TABLE NAME
--SOURCE QUERY
SEL COL1, COL2, COL3, COL4,
COL5, COL6, COL7 WHERE COL5 = '2015-11-04 16:24:00.000000' FROM SOURCE TABLE;
--TARGET TABLE NAME
--TARGET QUERY
SEL COLUMN1, COLUMN2, COLUMN3, COLUMN4,... (4 Replies)
Hi there,
I'm trying to create a script that will accept multiple inputs by copying and pasting the strings from a notepad, hit Enter key and output the string to a text file.I'm thinking of using the read command however it will just simply get the first line.
Apologies but got no idea how... (7 Replies)
Hi,
Can anyone help me for merge the following multi-line log which beginning with a " and line ending with ": into one line.
*****Original Log*****
087;2008-12-06;084403;"mc;;SYHLR6AP1D\LNZW;AD-703;1;12475;SYHLR6AP1B;1.1.1.1;0000000062;HGPDI:MSISDN=12345678,APNID=1,EQOSID=365;... (3 Replies)
Discussion started by: rajeshlinux2010
3 Replies
LEARN ABOUT OSX
pgrep
PKILL(1) BSD General Commands Manual PKILL(1)NAME
pgrep, pkill -- find or signal processes by name
SYNOPSIS
pgrep [-Lafilnoqvx] [-F pidfile] [-G gid] [-P ppid] [-U uid] [-d delim] [-g pgrp] [-t tty] [-u euid] pattern ...
pkill [-signal] [-ILafilnovx] [-F pidfile] [-G gid] [-P ppid] [-U uid] [-g pgrp] [-t tty] [-u euid] pattern ...
DESCRIPTION
The pgrep command searches the process table on the running system and prints the process IDs of all processes that match the criteria given
on the command line.
The pkill command searches the process table on the running system and signals all processes that match the criteria given on the command
line.
The following options are available:
-F pidfile Restrict matches to a process whose PID is stored in the pidfile file.
-G gid Restrict matches to processes with a real group ID in the comma-separated list gid.
-I Request confirmation before attempting to signal each process.
-L The pidfile file given for the -F option must be locked with the flock(2) syscall or created with pidfile(3).
-P ppid Restrict matches to processes with a parent process ID in the comma-separated list ppid.
-U uid Restrict matches to processes with a real user ID in the comma-separated list uid.
-d delim Specify a delimiter to be printed between each process ID. The default is a newline. This option can only be used with the
pgrep command.
-a Include process ancestors in the match list. By default, the current pgrep or pkill process and all of its ancestors are
excluded (unless -v is used).
-f Match against full argument lists. The default is to match against process names.
-g pgrp Restrict matches to processes with a process group ID in the comma-separated list pgrp. The value zero is taken to mean the
process group ID of the running pgrep or pkill command.
-i Ignore case distinctions in both the process table and the supplied pattern.
-l Long output. For pgrep, print the process name in addition to the process ID for each matching process. If used in conjunction
with -f, print the process ID and the full argument list for each matching process. For pkill, display the kill command used for
each process killed.
-n Select only the newest (most recently started) of the matching processes.
-o Select only the oldest (least recently started) of the matching processes.
-q Do not write anything to standard output.
-t tty Restrict matches to processes associated with a terminal in the comma-separated list tty. Terminal names may be of the form
ttyxx or the shortened form xx. A single dash ('-') matches processes not associated with a terminal.
-u euid Restrict matches to processes with an effective user ID in the comma-separated list euid.
-v Reverse the sense of the matching; display processes that do not match the given criteria.
-x Require an exact match of the process name, or argument list if -f is given. The default is to match any substring.
-signal A non-negative decimal number or symbolic signal name specifying the signal to be sent instead of the default TERM. This option
is valid only when given as the first argument to pkill.
If any pattern operands are specified, they are used as regular expressions to match the command name or full argument list of each process.
Note that a running pgrep or pkill process will never consider itself as a potential match.
EXIT STATUS
The pgrep and pkill utilities return one of the following values upon exit:
0 One or more processes were matched.
1 No processes were matched.
2 Invalid options were specified on the command line.
3 An internal error occurred.
SEE ALSO kill(1), killall(1), ps(1), flock(2), kill(2), sigaction(2), pidfile(3), re_format(7)HISTORY
The pkill and pgrep utilities first appeared in NetBSD 1.6. They are modelled after utilities of the same name that appeared in Sun Solaris
7. They made their first appearance in FreeBSD 5.3.
AUTHORS
Andrew Doran <ad@NetBSD.org>
BSD February 11, 2010 BSD