I see no "performance issue", just a "ps"-output. To assess the performance situation of your system it would be necessary to the output of:
and, depending on the configuration of your system ("lscfg") probably some other.
Anyways, to kill the processes is easy. You see the columns labeled PID in your output:
then wait a few seconds, issue another "ps". If <pid> isn't gone:
I still have serious doubts that this will help your situation any and i fear it might make you situation even worse, but there you go. My recommendation is not to do it, but you are free to do as you please.
Does anyone know what the equivalent command to pwait on Solaris is on DG/UX. I need my script to kick off a process and wait till it is complete before continuing with the script. (4 Replies)
Hi,
is-it normal to have 86% of CPU for wait commande :
ps aux| head -20
UTIL PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 516 86,6 0,0 12 12 - A 02 nov 2088:03 wait
oralfa01 54422 4,6 1,0 68044 39868 - A 09:20:06 2:27 oracleALFA01
If... (3 Replies)
Did not use 'wait' yet.
How I understand by now the wait works only for child processes, started background.
Is there any other way to watch completion of any, not related process (at least, a process, owned by the same user?)
I need to start a background process, witch will be waiting... (2 Replies)
hi,
i want to know cpu utilizatiion per process per cpu..for single processor also if multicore in linux ..to use these values in shell script to kill processes exceeding cpu utilization.ps (pcpu) command does not give exact values..top does not give persistant values..psstat,vmstat..does njot... (3 Replies)
Hi,
I collect statistics with nmon. I'm very suprised about % wait of processor.
Number Of Processors: 4
Processor Clock Speed: 4204 MHz
Do U have an idea about % wait ?
│ 0----------25-----------50----------75----------100 ... (1 Reply)
Hi All,
I have two ksh script. 1st script calls the 2nd script and the second script calls an 'C' program.
I want 1st script to wait until the 'C' program completes.
I cant able to get the process id for the 'C' program (child process) to make the 1st script to wait for the second... (7 Replies)
HI All
Am on Sun OS.While trying to start a process , we could see that the port is idle and we are not able to find the process holding that port.
Below is the result we get after using netstat command. lsof command is not yet installed in our machine.
netstat -a | grep "port no"... (5 Replies)
Hi ,
In a server /tmp has almost reached 75% and i can see the File system utilization is 48Mb only , so i believe some process is using the /tmp space. I would like to know which process is using /tmp space.
# df -h /tmp
Filesystem size used avail capacity Mounted on
swap ... (9 Replies)
Hi,
I can't seem to make sense of this. My wait time is showing really high but vmstat's and topas are showing normal usage.
ps aux
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 9961810 5680.7 0.0 448 384 - A Dec 16 6703072:12 wait
... (2 Replies)
Hello All,
The system concerned has multiple processes communicating with each other using shared memory. These processes use semaphores to protect data being used amongst them. The "key" would uniquely identifies the particular semaphore corresponding to a resource for the various processes.
... (2 Replies)
Discussion started by: saptarshi
2 Replies
LEARN ABOUT BSD
kill
KILL(1) General Commands Manual KILL(1)NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO csh(1), ps(1), kill(2), sigvec(2)BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)