Sponsored Content
Top Forums UNIX for Advanced & Expert Users When kill doesnt work, how to kill a process ? Post 302073413 by System Shock on Friday 12th of May 2006 04:24:26 PM
Old 05-12-2006
Kinda hard to tell what process was the parent, since it obviously ended and you only have a ppid to go by, and unless these are recorded... anyway, net time, try the wait command. I've seen times up to 20 minutes until the zombie goes away, but it beats rebooting.
 

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
exit(2) 							System Calls Manual							   exit(2)

NAME
exit(), _exit(), _Exit() - terminate a process SYNOPSIS
Parameters status The values of status can be or as described in or any other value, although only the least significant 8 bits (that is, status is available to a waiting parent process. DESCRIPTION
The function first calls all functions registered by in the reverse order of their registration. Each function is called as many times as it was registered. If a function registered by a call to fails to return, the remaining registered functions are called and the rest of the processing is not completed. terminates the calling process and passes status to the system for inspection {see wait(2)}. Returning from main in a C program has the same effect as the status value is the function value returned by main (this value is undefined if main does not take care to return a value or to call explicitly). If the calling process is multithreaded, all threads/lightweight process in the process will be terminated. cannot return to its caller. The result of an call during exit processing is undefined. The functions and are equivalent, except that calls functions registered by and flushes standard I/O buffers, while does not. The function is equivalent to The functions and terminate the calling process with the following consequences. The exact order of these consequences is unspecified. All file descriptors, directory streams, conversion descriptors, and message catalog descriptors open in the calling process are closed. All files created by are removed (see tmpfile(3S)). If the parent process of the calling process is executing a or it is notified of the calling process's termination, and the low- order eight bits; i.e., bits 0377 of status are made available to it (see wait(2)). If the parent process of the calling process is not executing a or and does not have set to the calling process is transformed into a zombie process. A zombie process is a process that only occupies a slot in the process table. It has no other space allocated either in user or kernel space. Time accounting information is recorded for use by (see times(2)). The parent process ID is set to the process ID of the initialization process (aka for all of the calling process's existing child processes and zombie processes. This means the initialization process inherits each of these processes. Threads/LWPs terminated by a call to shall not invoke their cancellation cleanup handlers or their thread specific data destructor functions. Each attached shared memory segment is detached and the value of in the data structure associated with its shared memory identifier is decremented by 1 (see shmop(2)). For each semaphore for which the calling process has set a semadj value (see semop(2)), that semadj value is added to the value of the specified semaphore. If the process has a process, text, or data lock, an is performed, see plock(2). An accounting record is written on the accounting file if the system's accounting routine is enabled (see acct(2)). A signal is sent to the parent process. If the calling process is a controlling process, the signal is sent to each process in the foreground process group of the control- ling terminal belonging to the calling process. The controlling terminal associated with the session is disassociated from the ses- sion, allowing it to be acquired by a new controlling process. If the exit of the calling process causes a process group to become orphaned, and if any member of the newly-orphaned process group is stopped, all processes in the newly-orphaned process group are sent and signals. If the current process has any child processes that are being traced, they are sent a signal. AUTHOR
was developed by HP, AT&T, and the University of California, Berkeley. and were developed by HP. SEE ALSO
sh(1), acct(2), close(2), plock(2), semop(2), shmget(2), shmop(2), sigaction(2), times(2), vfork(2), wait(2), wait3(2), waitpid(2) atexit(3), fclose(3), pthread_cancel(3T), pthread_exit(3T), pthread_key_create(3T), signal(5). See exit conditions STANDARDS CONFORMANCE
exit(2)
All times are GMT -4. The time now is 09:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy