Sponsored Content
Full Discussion: Syntax error with ps command
Top Forums Shell Programming and Scripting Syntax error with ps command Post 302990005 by mohtashims on Friday 20th of January 2017 01:37:09 PM
Old 01-20-2017
RedHat Syntax error with ps command

i am trying the blow command in vain on Linux Terminal.

Code:
kill -9 `ps -eaf | grep weblogic.NodeManager | grep wls103 | awk '{print $2}'`
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

kill -9 $(ps -eaf | grep weblogic.NodeManager | grep wls103| awk '{print $2}')
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

kill -9 ps -eaf | grep weblogic.NodeManager | grep wls103 | awk '{print $2}'
bash: kill: ps: arguments must be process or job IDs

Can you please suggest what will work ?
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

until command syntax error

Hi there. I spent too much time away from Unix, now I can't remember how to issue a simple until command in ksh :mad: could you tell me what is wrong with the following code sample: export v = "1" until do echo 'executing repeat_until' v = `expr $v + 1` done I've... (3 Replies)
Discussion started by: 435 Gavea
3 Replies

2. Shell Programming and Scripting

if else command syntax error

can anyone tell me what`s going wrong with my if else statement? set exam=(AAA BBB CCC) foreach ii ($exam) if ($ii -eq "AAA") do echo "PASS" else echo "FAILED" done end (4 Replies)
Discussion started by: c0384
4 Replies

3. UNIX for Dummies Questions & Answers

awk Shell Script error : "Syntax Error : `Split' unexpected

hi there i write one awk script file in shell programing the code is related to dd/mm/yy to month, day year format but i get an error please can anybody help me out in this problem ?????? i give my code here including error awk ` # date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies

4. AIX

nim mksysb error :/usr/bin/savevg[33]: 1016,07: syntax error

-------------------------------------------------------------------------------- Hello, help me please. I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? : Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies

5. Shell Programming and Scripting

bash syntax error: command not found

I am trying to create a shell that asks the user to enter their name, and compare it to my own by saying we have the same name or saying my name and that they have a nice name too. Here is my script... #!/bin/bash-x echo "Enter your name". read name if then echo "My name is Adam too"... (1 Reply)
Discussion started by: amaxey45
1 Replies

6. Shell Programming and Scripting

Syntax error using do command

i have the following do command: while IFS =: read printer drv IP port do echo -e "$ printer: \ n \ drv: \ t $ drv \ n \ IP: \ t $ IP \ n \ port: \ t $ port \ n \" done < diffs.txt receiving the following error: syntax error at line 37 : `do' unmatched something is... (2 Replies)
Discussion started by: ggoliath
2 Replies

7. Shell Programming and Scripting

Syntax error piping to bc on command line - works when assigned to var

I have a script which outputs some timing data a line at a time. There are approx. 10 lines echoed, each line looks something like this: 0.741 http://checkip.dyndns.org 94.170.119.226Since I needed to add all the values in the first column, I piped the output to grep, matching and printing the... (7 Replies)
Discussion started by: gencon
7 Replies

8. Shell Programming and Scripting

Getting syntax error while running awk command

Hello Gurus, I am firing the below command : df -g | grep -v var| awk '{ (if $4 > 90% ) print "Filesystem", $NF,"over sized";}' But I am getting the below error:- ====== syntax error The source line is 1. The error context is {if ($4 > >>> 90%) <<< awk: The... (9 Replies)
Discussion started by: pokhraj_d
9 Replies

9. UNIX for Advanced & Expert Users

Command syntax error in cron

SCO OSR 507, user's shell is old Bourne sh The same command is OK when run using now, but fails when run in cron, see below: 1) using now, see how it worked and I see resulting DT=2018 in the mail $ at now { dt=`/usr/gnu/bin/date '+%Y'`; echo "DT=$dt"; } job 1522867418.a-6605:0 at Wed... (2 Replies)
Discussion started by: migurus
2 Replies
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)
All times are GMT -4. The time now is 08:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy