Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

tkill(1) [xfree86 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)

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)
Man Page

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script to kill stranded/orphan process by users.

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)
Discussion started by: rjohnson
4 Replies

2. Shell Programming and Scripting

Perl script to kill the process ID of a command after a certain period

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)
Discussion started by: Pouchie1
7 Replies

3. Solaris

unkillable format process

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)
Discussion started by: plmachiavel
2 Replies

4. HP-UX

Way to find source of a kill -9 in HP-UX

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)
Discussion started by: aixusrsys
0 Replies

5. Solaris

Way to find source of a kill -9 in Solaris

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)
Discussion started by: aixusrsys
3 Replies