Killing a stubborn process...


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Killing a stubborn process...
# 8  
Old 01-29-2002
Your ps output says that the process is waiting on the physio routine. That means it is doing a read or a write to disk and is waiting for it to complete. Unix will not allow the process to die until the i/o completes. This is how it fulfills its promise of atomic disk i/o. I would suspect a hardware error in combination with a disk driver with poor error handling. The other possibility is a pathetic disk driver.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Killing the process ID's

Hi , I have a list of application process id's. Is there a way to kill all the process listed below using the script, except the once which are starting with " Genesis " adm 1522 ABC_Process.tra adm 1939 Genesis_Process.tra adm 2729 Genesis_Archive.tra adm 3259 xyz_Process.tra (5 Replies)
Discussion started by: murali1687
5 Replies

2. UNIX for Dummies Questions & Answers

Killing the shell Process

I was just playing with the processes and suddenly a question striked my mind: What will happen if we kill directly the shell process?? :rolleyes: Do anyone know? Will the system shutdown? Or the system wont let it be killed? (5 Replies)
Discussion started by: paras.oriental
5 Replies

3. UNIX for Advanced & Expert Users

Killing A Stopped Process

UNIX Tutorial Five % kill %jobnumber Does that not work on a stopped process? I've tried to kill a stopped process and it is not working. Or do you need a certain type of shell for this to work? I don't see anything about this in my man pages. (3 Replies)
Discussion started by: cokedude
3 Replies

4. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies

5. Shell Programming and Scripting

Killing process!!!!

Hi friends, i m in big trouble.... i have one script which connects two server ...like below.. script1.sh ------------------------------------- bash test.sh & eval x=$@ export x=`echo $x` #echo $x # ssh user@8.2.5.6 bash /mbbv/location/script.sh $x|sed '/Binary file/d'... (1 Reply)
Discussion started by: Shahul
1 Replies

6. Shell Programming and Scripting

Killing process and children

Hi all, I have been searching all day for a nice solution to this problem. I have three scripts. A start script, a child script and a stop script. Script A (scripta.sh) Its Child Script B (scriptb.sh) Script C (kill_process.sh $PID) Script A correctly traps the kill command sent from... (6 Replies)
Discussion started by: mark007
6 Replies

7. UNIX for Dummies Questions & Answers

killing the process

Hi, First, I am running a scipt.While the script is running I realize that I dont want the script to be run so I am killing the script externally.Before the process gets terminated or killed it should delete all the temporary files created by the script.How to do this?Can anyone help me? ... (3 Replies)
Discussion started by: arthi
3 Replies

8. Shell Programming and Scripting

Killing of a process and send a mail if the process doesnot come up within 2 minutes

Hi Friends, I am new to this forum as well as new to shell scripting. I have a problem here and i need someone to solve this. Let us consider there are two processes(abc & def).There is a script which kills these two processes(i.e killtheprocess abc). Here abc is the argument . There is a... (1 Reply)
Discussion started by: Prince89
1 Replies

9. Solaris

Reg process of killing

Dear All, I have one doubt - when u use netstat -na | grep 8080 to know the status of 8080 ports.when it is listed someone is accessing the 8080 ports like this *.8080 *.* 0 0 64000 0 LISTEN 172.19.69.39.8080 172.19.50.20.1929 65535 ... (6 Replies)
Discussion started by: shanshine
6 Replies

10. UNIX for Dummies Questions & Answers

killing a process

I can kill running processes on my linux red hat system using ctrl-c but cannot do it from command line of another terminal using kill -2 pid. Although I can kill them from command line using kill -9 pid and other signals. I would like to do it using the kill -2 pid. Thanks for your suggestions (6 Replies)
Discussion started by: bbhayana
6 Replies
Login or Register to Ask a Question
vlimit(3)						     Library Functions Manual							 vlimit(3)

Name
       vlimit - control maximum system resource consumption

Syntax
       #include <sys/vlimit.h>

       vlimit(resource, value)

Description
       This facility has been superseded by

       Limits  the  consumption by the current process and each process it creates to not individually exceed value on the specified resource.	If
       value is specified as -1, then the current limit is returned and the limit is unchanged.  The resources which  are  currently  controllable
       are:

       LIM_NORAISE    Pseudo-limit; if set nonzero then the limits may not be raised.  Only the super-user may remove the noraise restriction.

       LIM_CPU	      The maximum number of cpu-seconds to be used by each process.

       LIM_FSIZE      The largest single file which can be created.

       LIM_DATA       The maximum growth of the data+stack region via beyond the end of the program text.

       LIM_STACK      The maximum size of the automatically-extended stack region.

       LIM_CORE       the size of the largest core dump that will be created.

       LIM_MAXRSS     a  soft  limit for the amount of physical memory (in bytes) to be given to the program.  If memory is tight, the system will
		      prefer to take memory from processes which are exceeding their declared LIM_MAXRSS.

       Because this information is stored in the per-process information this system call must be executed directly by	the  shell  if	it  is	to
       affect all future processes created by the shell; limit is thus a built-in command to

       The  system  refuses to extend the data or stack space when the limits would be exceeded in the normal way.  A break call fails if the data
       space limit is reached, or the process is killed when the stack limit is reached.  Since the stack cannot be extended, there is no  way	to
       send a signal.

       A file I/O operation which would create a file which is too large will cause a signal SIGXFSZ to be generated, this normally terminates the
       process, but may be caught.  When the cpu time limit is exceeded, a signal SIGXCPU is sent to the offending process; to allow  it  time	to
       process the signal it is given 5 seconds grace by raising the cpu time limit.

Restrictions
       If LIM_NORAISE is set, then no grace should be given when the CPU time limit is exceeded.

See Also
       csh(1)

																	 vlimit(3)