Michael Trausch wrote:
> guybas@yahoo.com wrote:
> 
Something like??
while :
do
prog &
kill -9 $!
done

I guess adding a 'sleep' command to the loop would thwart your speed
measurements.
[vbcol=seagreen] 

Memory leaks in applications cuase the memory consumption to increase
and performance to degrade. We sometimes kill processes and restart the
application to free up leaked memory.

If 'kill' removes all traces of the user process, then the memory leak
could only be in the kernel.
[vbcol=seagreen] 

What resources are we talking about? Normal memory should be reclaimed
when a process terminates, and so should open files and sockets. Shared
memory, message queues and semaphores remain in use if the program does
not release them properly.
[vbcol=seagreen]
> What is happening to the process when you kill it?  Does it remain in
> the process list as a zombie?  Is its parent cleaning up after it?  What
> is its parent?

A zombie process uses up no resources except for the process table
entry. However, if a process 'hangs' in a system call that never
completes, the kill signal is not delivered and resources remain in use.

> If you could show or tell more about it, that'd be helpful.
>
> 	- Mike

Indeed it might,


Daniel

[ Post a follow-up to this message ]