What state is the process in? How do you know it is swapped out? What
problem is this causing?
If the parent crashed, then init should inherit the child as its own,
and it AFAIK does reap dead children periodically.
If the process shows up as <defunct> because the parent is not reaping
it, then there should be no memory associated with it any longer
(actually, there is enough to give the hint a process is still there,
but the address space should have already been reclaimed, and what's
left of the process now uses the kernel's address space until the parent
can be notified).
If you really want to force it into memory, then temporarily removing
your swap device and re-adding it is one way of trying this, but may
fail if you actually need the swap space. It's also a very heavy handed
way of doing it ;-)
Regards,
Brian
Mike DeMarco wrote:
kill doesn't work?
max
Nothing to kill, the process was swapped out and the parent crashed out so
there is no longer a owner of the swapped out process. It remains in swap until
the next reboot at which time the kernel no longer has any idea about it so the
swap space is free. I am looking for a tool that would let me examine the swap
space allocations that the kernel must know about and send out a reaper to
reclaim the space and tell the kernel to mark it as free.
Tools to examine swapped out processes seem to be lacking.
--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG
_______________________________________________
opensolaris-discuss mailing list
[email protected]
