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)
Check Out this Related Man Page
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)
I have customers on our AIX/UNIX node startup a process that becomes stranded or orphaned and must be killed. I would like to create a script to check for these orphan processes and kill them. I can have cron run this job. The customers process will run and after 24 hours time out leaving an... (4 Replies)
I have a script ( run by user ) that can find some user dead process ( like below ) , then another script will kill all these process, however , I found that one of these process is the user self login process ( pid : 58741 ) , therefore , when the script try to kill these dead process , it may be... (1 Reply)
Is there a way I can run a command that will run in the kernel or in the memory and automatically kill certain scripts if they get to <defunct> processes, without having to be monitoring the server manually?
I have a Perl script which runs for 20k members and normally does not have any problems,... (2 Replies)
Hi All,
I have started my processes through SMF functionality.
It gets started successfully.
But when I kill my processes, it's getting restarted. But in Solaris 9 and below if I kill it will not get restarted.
In Solaris 10 it should not get restarted L
How can I perform the operation... (5 Replies)
All,
I am trying to build a script in perl that will alllow me to pass the IP address to a ping command and redirect the output to a file and then kill that process after a certain period of time.
let's say, I call my script ping.pl, I would like to be able to run it like this for example :... (7 Replies)
Hi gurus,
I can not seem to be able to run format completely on my t2000 (Sol 10), it just hangs there and I cannot kill it.
I know that it is probably trapped in the kernel somewhere (far from the user space) and this is the reason i can not kill it but I would like to determine how to know... (2 Replies)
Hey,
Solaris 10, trying to track down which processes are using all the kernel. Top is showing much kernel (compared to user) cpu. But haven't had luck trying to find a command that shows specific (lets say top 10 current) processes using up the CPU via kernel.
I'd really like just top with... (1 Reply)
Hello Guys,
Someone or, some tool has killed the application process with signal 9 (kill -9) . How to track that in HP-UX?
On AIX we can use light-weight tool called ProbeVue to track it but not sure how to do it on HP-UX. Appreciate your help.
Kelly
Closed because this is... (0 Replies)
Hello Guys,
Someone or, some tool has killed the application process with signal 9 (kill -9) . How to track that in Solaris?
On AIX we can use light-weight tool called ProbeVue to track it but not sure how to do it on Solaris. Appreciate your help.
Kelly (3 Replies)
Hi Guys
I am running a small script to find a process id , ask user if they want to kill the process and then action it Yes or no
Here is what i have
#/bin/bash
ps -l | grep -i $1 | awk '{print "Process id of '$1' is "$4""}'
echo "Do you want to kill this process (Y/N)"
read action... (10 Replies)
Hi Team ,
I have one process named as cec_analysiseool that is running on unix box machine now i want to kill this process so please advise what will be the ideal command to kill this , what i have tried is :confused:
kill -9 `ps -ef | grep cec_analysiseool | grep -v grep | awk '{print $2}'` (2 Replies)