Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

compare two dates

I have a log file with date format like 10-Oct-02 13:20:29 ..... at the beginning of each line in the log file, and I need to grep data from this file to list the lines with date no longer than one days. I tried to use awk to do this but it looks very complicated to do it. Is there... (6 Replies)
Discussion started by: wchen
6 Replies

2. Solaris

some questions on 310-015

hi can any1 pls ans these questions 22. Which two statements about the functionality of the syslogd daemon are true? (Choose two) A. Error messages can only be logged locally in a system log. B. The kernel, daemons, and syslogd each write directly to a system log. C. Syslogd can write... (1 Reply)
Discussion started by: azeem_3001
1 Replies

3. Shell Programming and Scripting

A small project with bash script and craigslist

Before I start, I'm posting this for community knowledge, not to offend anyone. I thought it was an interesting project so that's why I'm sharing it. In the notorious erotic classified ads of craigslist, thousands of individuals post classifieds, using the internet to sell themselves with an... (0 Replies)
Discussion started by: hexpill
0 Replies

4. AIX

aix cert 223 need help.

Hi, a friend of mine passed there 223 last year and they gave me there testkiller document which was 65 questions, i am looking at doing my 223 exam and i have gone to testkiller recently and noticed there is an updated version which is now 383 questions. I did the ibm pre-exam and all the... (1 Reply)
Discussion started by: rorted
1 Replies

5. AIX

High CPU utilization by a pro*C process

Hi , we upgarded our AIX from 5.3 to 6.1 and upgraded our xlc compiler from ver 6.0 to 9.0 . After this upgrade one of our pro*C program is utilizing around 20% of the CPU. Before upgarde its using only 0.2 %. when i try to debug using the truss command i got the below error. $... (6 Replies)
Discussion started by: mugunthanvh
6 Replies

6. Shell Programming and Scripting

Write a scripts to kill idle user for 60 min. & email user list to admin in text file

Folks, I have written one script for following condition by referring some of online post in this forum. Please correct it if I'm missing something in it. (OS: AIX 5.3) List the idle user. (I used whoidle command to list first 15 user and get username, idle time, pid and login time).... (4 Replies)
Discussion started by: sumit30
4 Replies

7. Shell Programming and Scripting

Grab exactly one byte from a FIFO, at random intervals

I want to develop a script of the following form: #!/bin/bash # Function 'listen' opens a data stream # which stores all incoming bytes in # a buffer, preparing them to be # grabbed by a following function # which appears at random # intervals during the execution of # the script ... (11 Replies)
Discussion started by: vomv1988
11 Replies