Sponsored Content
Top Forums Programming kill(0,-9) don't kill the process Post 302122076 by umen on Tuesday 19th of June 2007 05:11:43 AM
Old 06-19-2007
hi and thanks for the reply after fixing this its working great
but one thing .. im getting
"Killed" stdout after kill is done , how can i remove this print?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

When kill doesnt work, how to kill a process ?

Hi All, I am unable to kill a process using kill command. I am using HP-UX system. I have tried with kill -9 and i have root privilages. How can i terminate this daemon ? ? ? Regards, Vijay Hegde (3 Replies)
Discussion started by: VijayHegde
3 Replies

2. Shell Programming and Scripting

how to start a process and make it sleep for 5 mins and then kill that process

how to start a process and make it sleep for 5 mins and then kill that process (6 Replies)
Discussion started by: shrao
6 Replies

3. Shell Programming and Scripting

Kill a process without using kill command

Sorry, posted the question in other forum. (0 Replies)
Discussion started by: sudhamacs
0 Replies

4. Linux

Kill a process without using kill command

I want to Kill a process without using kill command as i don't have privileges to kill the process. I know the pid and i am using Linux 2.6.9 OS. (6 Replies)
Discussion started by: sudhamacs
6 Replies

5. Shell Programming and Scripting

Shell Script to Kill Process(number of process) Unix/Solaris

Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it This is how we execute the script (and this is the requirement) ... (2 Replies)
Discussion started by: jonnyvic
2 Replies

6. UNIX for Dummies Questions & Answers

Script to start background process and then kill process

What I need to learn is how to use a script that launches background processes, and then kills those processes as needed. The script successfully launches the script. But how do I check to see if the job exists before I kill it? I know my problem is mostly failure to understand parameter... (4 Replies)
Discussion started by: holocene
4 Replies

7. Windows & DOS: Issues & Discussions

Kill a process

Hi, How can I terminate process using vbscript. PLEASE NOTE, I need to terminate process that runs under windows 64-bit environment as native 64 (not using select * from win_32_Process) (3 Replies)
Discussion started by: cratercrabs
3 Replies

8. Solaris

Cannot kill a process with kill -9

Hello everyone, I have a process that I want to kill. I have tried kill-9 PID but it doesn't work. I have tried preap PID but it doesn't work too. The parent of my process is the process whose PID is 1, so I can't kill it. My OS is a Solaris 9. Can anyone help me understand what's going... (3 Replies)
Discussion started by: adilyos
3 Replies

9. Shell Programming and Scripting

Kill an specific process ID using the KILL and GREP commands

Good afternoon I need to KILL a process in a single command sentence, for example: kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'` That sentence Kills the process ID corresponding to the program CAL255.4ge. However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies

10. Shell Programming and Scripting

Why don't kill the script after 5s?

# watchdog process mainpid=$$ (sleep 5; kill $mainpid) & watchdogpid=$! sleep 100 kill $watchdogpid The sleep isn't be killed, I want the script to be killed ---------- Post updated at 03:03 AM ---------- Previous update was at 12:04 AM ---------- I just modify the format of my... (1 Reply)
Discussion started by: yanglei_fage
1 Replies
HBOOT(1)                                                             LAM TOOLS                                                            HBOOT(1)

NAME
hboot - Start LAM on the local node. SYNOPSIS
hboot [-dhstvNV] [-c conf] [-I inet_topo] [-R rtr_topo] OPTIONS
-d Turn on debugging. This implies -v. -h Print the command help menu. -s Close stdio of child processes. -t Terminate (tkill(1)) any previous LAM session before starting. -v Be verbose. -N Go through the motions but do not actually take any action. -V Format and print the process schema. -c conf Use conf as the process schema. -I inet_topo Set the $inet_topo variable in the process schema. -R rtr_topo Set the $rtr_topo variable in the process schema. DESCRIPTION
Most MPI users will probably not need to use the hboot command; see lamboot(1). The hboot tool can be understood as a generic utility that starts multiple processes on the local node, based on information in a process schema. It is not restricted to starting LAM. It is part of the startup sequence preformed by lamboot(1). A process schema is a description of the processes which constitute the operating system on a given node. Naturally, the process schema used by hboot should be the one that describes LAM on a node. The grammar of the process schema is described in conf(5). When starting LAM on a remote machine using rsh(1), the open file descriptors of the processes started by hboot must be closed in order for rsh(1) to exit. This is done by using the -s option. The -t option can be used to force a tkill(1) on the machine before attempting to start LAM. This feature is used by lamboot(1) to handle the case where a user might start a machine a second time without using lamwipe(1) to terminate the previous LAM session. The -I and -R options set their respective variables to the given values. The $inet_topo variable is typically used by the LAM Internet datalinks that communicate with other nodes. The $rtr_topo variable is passed to the LAM router that handles network and topology informa- tion. The variables can also be set in the process schema file (see conf(5)) but their values are overridden by the command line options. When LAM is started, the kernel records all processes that attach to it, including all the processes in the process schema. It is the job of tkill(1) to use this information to remove these processes from the node. EXAMPLES
hboot -v Start LAM on the local node with the default process schema. Report about every step as it is done. hboot -c myconfig Boot the local node with the custom process schema, myconfig. FILES
laminstalldir/etc/lam-conf.lamd default node process schema, where "laminstalldir" is the directory where LAM/MPI was installed laminstalldir/etc/lam7.1.4helpfile Default location for help file for diagnostic messages that hboot may generate. /tmp/lam-$USER@hostname kill file for the LAM session on machine hostname, where $USER is the userid. DIAGNOSTICS
Using ps(1) after hboot will display, among others, the LAM processes that have been started. They may be killed one by one with kill(1), or all at once by killing the LAM kernel process with a HUP signal. The preferred method is to use the LAM tool tkill(1) which should kill them all at once, and also remove the kill file. New users should make liberal use of ps(1) to gain confidence that the system is working properly. In a disaster, ps(1) and kill(1) are your only hope of recovery. SEE ALSO
lamboot(1), tkill(1), conf(5), lam-helpfile(5) LAM 7.1.4 July, 2007 HBOOT(1)
All times are GMT -4. The time now is 11:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy