> Any ideas???? > ...besides a reboot of course. Are there any child processes or otherwise associated other programs that it might be waiting for the death of? What was the command-line/script that spawned this job? Are there any other hung processes?