Sponsored Content
Top Forums UNIX for Advanced & Expert Users When kill doesnt work, how to kill a process ? Post 302073218 by Perderabo on Thursday 11th of May 2006 04:36:47 AM
Old 05-11-2006
If it has died and is now a zombie, killing the parent process will cause it to be re-parented to init which will reap it. But if it is sleeping at a high kernel priority, the only general answer is to reboot the system. Since you're on HP-UX, you should use glance to examine the process and determine what it is waiting for. Then there is some chance that you can correct it. For example, if it is trying to close a tape drive that has been powered off, bringing the tape drive back online may allow the close to succeed. Or maybe it is trying to write to /dev/console and someone typed an X-off (control s), so typing an X-on (control q) may allow the write to finish. If it is doing disk i/o to an NFS mounted filesystem with nointr, fixing the NFS server or the network may do it. Or maybe it is a bug in the kernel and so you want to identify what resource it is waiting for and then check for patches that look applicable. This won't help kill the particular process you have now, but patching the kernel would insure it doesn't keep on happening.
 

10 More Discussions You Might Find Interesting

1. 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

2. Programming

kill(0,-9) don't kill the process

Hi all i have simple c program , when i wish to kill the app im using kill(0,-9) , but it seams this command don't do any thing and the program. just ignore it . what im doing wrong here ? im using HP-UX ia64 Thanks (9 Replies)
Discussion started by: umen
9 Replies

3. Solaris

How to Kill a Process

Hi, how can i kill one running process, how can i get the process id thanks .BJ (5 Replies)
Discussion started by: bennichan
5 Replies

4. Shell Programming and Scripting

When kill [pid] does not work...

Hi, On my Linux machine, using Bash, I sometimes run into a situation where doing the following does not seem to work at all. kermit@fastbox ~ $ ps -A | grep firefox-bin 5375 ? 00:06:57 firefox-bin <defunct> 5624 ? 00:00:00 firefox-bin kermit@fastbox ~ $ kill 5624... (7 Replies)
Discussion started by: kermit
7 Replies

5. 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

6. 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

7. 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

8. 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

9. 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

10. 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
AMTAPE(8)						      System Manager's Manual							 AMTAPE(8)

NAME
amtape - user interface to Amanda tape changer controls SYNOPSIS
amtape config command [ command options ] DESCRIPTION
Amtape performs tape changer control operations. It uses the underlying tape changer script defined by the tpchanger option for a particu- lar Amanda configuration as specified by the config argument. Tape changers maintain a notion of the current and next slot for each configuration. These may or may not correspond to an actual physical state of the device, but do tend to minimize searching through the tape storage slots. If the desired tape is in the current slot, it is likely the next tape needed is in the next slot rather than at some random position in the storage slots. See the amanda(8) man page for more details about Amanda. COMMANDS
reset Reset the tape changer to a known state. The current slot is set to the first slot. Other device-specific side effects may occur. Some gravity stackers need to be reset to the top position by hand. This command notifies Amanda the stacker is back in that posi- tion. eject If a tape is loaded in the drive, it is ejected and returned to the slot from which it was loaded. clean If a cleaning tape is defined for the changer, it is used to clean the drive. show Show the contents of all slots. This can be slow. label label Search for and load the Amanda tape with label label. taper Perform the taper scan algorithm. Load the next tape in the configuration's tape sequence, or a fresh tape with a suitable label. device Display the name of the current tape device on stdout. current Display the current slot. update Update the changer label database, if it has one, to match the tapes now available. slot slot Eject any tape in the drive and put it away, then load the tape from slot slot and reset current. slot current Eject any tape in the drive and put it away, then load the tape from the current slot. slot prev Eject any tape in the drive and put it away, then load the tape from the previous slot and reset current. slot next Eject any tape in the drive and put it away, then load the tape from the next slot and reset current. slot first Eject any tape in the drive and put it away, then load the tape from the first slot and reset current. slot last Eject any tape in the drive and put it away, then load the tape from the last slot and reset current. slot advance Eject any tape in the drive and put it away. Advance current to the next tape, but do not load it. This is useful with non-gravity stackers to unload the last tape used and set up Amanda for the next run. If you just use eject, the current tape will be mounted again in the next run, where it will be rejected as being still in use, ejected and the next tape requested. Using slot next followed by eject does an unnecessary mount. Note: most changers optimize the slot commands to not eject the loaded tape if it is the one being requested. AUTHOR
James da Silva <jds@cs.umd.edu> University of Maryland, College Park SEE ALSO
amanda(8) AMTAPE(8)
All times are GMT -4. The time now is 01:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy