Hi Guys,
I was just wondering if anybody can help me with this problem.
OK, how we can get a value back from PL/SQL Script (not stored procedure/function)
See the below example: (for example aaa.sh)
#!/bin/ksh
VALUE=`sqlplus -s user/password@test_id <<EOF
@xxx.sq
EOF`
echo $VALUE
... (7 Replies)
hi all
my system is linux red hat
i have a script that runs some object .
the object return some code to the system
i see the code by writing echo $?
i want to ask in the script if $? equals 14
how shell is do that in the script
thanks (3 Replies)
Hi All,
Can anyone please let me know the syntax / how to pick up the Return Code ( RC) from the mailx command and return it to SAS uisng 'system()' function and '${?}'.
I am in a process to send the mail automatically with an attachment to bulk users. I have used 'Mailx' and 'Unencode'... (0 Replies)
Hi All
I have what seems to be something quite trivial but for the life of me can't work out a solution.
Basically, I have the following script that reads a version report that contains certain flags. If a condition is true, I want to print the value of column 2, sort them uniquely and return... (2 Replies)
Hi,
I have installed cygwin on my windows XP system. And I am trying to use the following code snippet:
set SERVER="grep JDBCConnectionPool config.xml | gawk -F; '{print $2}'"
sed -i 's/%SERVER%/WLMDEVDB1/' config.xml
But it doesn't work because at runtime %SERVER% gets replaced by "grep... (2 Replies)
Hi Everyone,
When i finish running
# echo `psql -t -U root databaseA -c "select a, b from book"`;
i get the output
107275 | 14 107301 | 2 107446 | 6 107820 | 77 107929 | 101
Would like to have the result like:
107275 | 14
107301 | 2
107446 | 6
107820 | 77
107929 | 101 (7 Replies)
Hello Everybody,
thanks in advance for spending some time in my problem.
My problem is this:
I want to call a java-Programm out of my shell skript, check if die return code is right, and split the output to the normal output and into a file.
The following code doesn't work right, because in... (2 Replies)
Hello EveryOne,
I am new to *ix. some could help to write a script.
Problem :- Have to ssh to so many client and check port or filesystem usage, so thinking to automate using script.
What i Need:- when i run script on my Launchpad server, it should
Should ask and SSH to user provided... (3 Replies)
Hi All,
There are 2 scripts A and B.
A --> It will invoke script B
B -->
It will generate below output.
100 - connected
105 - Not Connected
210 - Connected
I want to return this value to script A. Please advice. (4 Replies)
cmd()
{
echo " "
echo "$(whoami)@$(hostname):$(pwd)# $*"
results=`eval $*`
echo $results
}
I want to get the eval $* 's return value and pass it to a new variable $val, and get "eval $*" 's the ... (7 Replies)
Discussion started by: yanglei_fage
7 Replies
LEARN ABOUT MOJAVE
pkill
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