04-18-2013
Thanks , But i see a kill command in the script , is the script going to kill the top space using process under /tmp ? Well i just want them to be listed ! I dont want to kill them as they are application process
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Help ! - I have a process which I cannot find that is writing to /var/tmp every 10 minutes and filling up my partition, it is also filling up my wtmpx file. I have some software error correction for a faulty DIMM at the moment - is this likely to be causing this as well as over-loading my... (3 Replies)
Discussion started by: Mal
3 Replies
2. AIX
This is my first post, and I am new to the UNIX world. Hopefully this question won't be too lame.
I know that I can use topas to see the paging space used by some processes. I would like to script something that can add up the paging space used by process owned by or associated with an... (1 Reply)
Discussion started by: alntht
1 Replies
3. UNIX for Dummies Questions & Answers
OS: Unix or Linux
I (only) know the pid of the process which was running earlier (say 5 hrs back) but it is not running now.
Is there a way I could find the details of that process? (atleast the name of the process). Please let me know. (2 Replies)
Discussion started by: vijay.d
2 Replies
4. Solaris
Hi all,
We have a server having much processes running. It is very difficuilt to trace the exact consuming more memory. Howerver, it shows CPU usage in sequence but how memory?
Tried working with TOP command.
Please let me know if something not clear.
Thanks,
Deepak (5 Replies)
Discussion started by: naw_deepak
5 Replies
5. Solaris
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)
Discussion started by: Whiteboard
5 Replies
6. AIX
Hi all,
Have this performance Issue,
srvbd1]root]/]>ps vg | head -1 ; ps vg | grep -w wait
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
8196 - A 4448:23 0 384 384 xx 0 0 12.8 0.0 wait
53274 - A 4179:28 0 384 ... (9 Replies)
Discussion started by: gopeezere
9 Replies
7. AIX
Hello,
Below are the list of files
ls -lrt
total 16
lr-x------ 43 oracle dba 0 Dec 5 14:27 root -> /
lr-x------ 2 oracle dba 0 Dec 16 00:14 cwd -> /prodoragridcn_01/app/oracle/product/11203/dbs/
-r--r--r-- 1 oracle dba 0 Dec 16... (4 Replies)
Discussion started by: Vishal_dba
4 Replies
8. UNIX for Advanced & Expert Users
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
9. Shell Programming and Scripting
I am on SunOS and Linux
I need generic command to get complete process details from which i will eventually extract socket details (listen address and port)
ps -ef | ggrep -i server | ggrep -i mydomaindoes not yield a process that should have both the grep entries along with the listen... (8 Replies)
Discussion started by: mohtashims
8 Replies
10. Shell Programming and Scripting
Hi,
I have iPlanet 7.0 process running on Solaris system
SunOS mymac15.10 Generic_150400-59 sun4v sparc sun4v.
The link here suggests to use the below command to get process runtime details / health inorder to understand if the iPlanet process is hung or good.
/usr/bin/ps -o "pid ppid... (4 Replies)
Discussion started by: mohtashims
4 Replies
TKILL(1) LAM TOOLS TKILL(1)
NAME
tkill - Terminate LAM on one node.
SYNOPSIS
tkill [-dhvN] [-f killfile]
OPTIONS
-d Turn on debugging mode. This implies -v.
-h Print the command help menu.
-v Be verbose.
-N Pretend; do not take action.
-f killfile Use killfile as the name of the kill file.
DESCRIPTION
The tkill tool terminates the LAM session started by hboot(1) on the local node. tkill makes use of a kill file created by the LAM kernel,
which contains the process identifiers of every LAM process in ASCII format. A SIGHUP (see signal(3)) signal is sent to every process
listed in the kill file. tkill waits a short period of time for each process to die. By adding the debug option, the user can see the
final disposition of each process. The mission is accomplished if all processes end up dead.
In LAM, the first process to be killed is always the kernel. When the kernel receives its termination signal, it propagates the signal to
all of its constituent processes. Therefore, tkill will ordinarily be racing the kernel to kill all other processes. This redundant
aspect of tkill allows it to be used as a general purpose tool in association with hboot(1).
FILES
/tmp/lam-$USER@hostname the kill file, created by the kernel, where $USER is the userid, and hostname is the name of the local
machine
SEE ALSO
hboot(1), lam-helpfile(5)
LAM 7.1.4 July, 2007 TKILL(1)