Syntax error with ps command Post: 302990019

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

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

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

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

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

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

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

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

LEARN ABOUT FREEBSD

kill

KILL(1) 						    BSD General Commands Manual 						   KILL(1)

NAME

     kill -- terminate or signal a process

SYNOPSIS

     kill [-s signal_name] pid ...
     kill -l [exit_status]
     kill -signal_name pid ...
     kill -signal_number pid ...

DESCRIPTION

     The kill utility sends a signal to the processes specified by the pid operands.

     Only the super-user may send signals to other users' processes.

     The options are as follows:

     -s signal_name
	     A symbolic signal name specifying the signal to be sent instead of the default TERM.

     -l [exit_status]
	     If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status.

     -signal_name
	     A symbolic signal name specifying the signal to be sent instead of the default TERM.

     -signal_number
	     A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.

     The following PIDs have special meanings:

     -1      If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.

     Some of the more commonly used signals:

     1	     HUP (hang up)
     2	     INT (interrupt)
     3	     QUIT (quit)
     6	     ABRT (abort)
     9	     KILL (non-catchable, non-ignorable kill)
     14      ALRM (alarm clock)
     15      TERM (software termination signal)

     Some shells may provide a builtin kill command which is similar or identical to this utility.  Consult the builtin(1) manual page.

EXIT STATUS

     The kill utility exits 0 on success, and >0 if an error occurs.

EXAMPLES

     Terminate the processes with PIDs 142 and 157:

	   kill 142 157

     Send the hangup signal (SIGHUP) to the process with PID 507:

	   kill -s HUP 507

     Terminate the process group with PGID 117:

	   kill -- -117

SEE ALSO

     builtin(1), csh(1), killall(1), ps(1), sh(1), kill(2), sigaction(2)

STANDARDS

     The kill utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.

HISTORY

     A kill command appeared in Version 3 AT&T UNIX.

BUGS

     A replacement for the command ``kill 0'' for csh(1) users should be provided.

BSD
								  April 28, 1995							       BSD