Board index Linux

Task States; can't kill 'D' tasks

Task States; can't kill 'D' tasks

Post by bryan par » Thu, 21 Sep 1995 04:00:00



Hi, I am new to Linux. I am using Slackware 2.3.0, and have successfully
installed it and am having a ball with disk sets A, AP and D. I had a
glitch the other day when searching tar archives looking for a specific
file. I would CTRL-C to quit searching when it was obvious that I was
looking at the wrong floppy. Then tar got hung up and froze, when I
flipped over to another console I noticed that the state of the task
reported by the top command indicated a 'D', which I learned as
"un-interruptable sleep". I could not kill this task, and bogged the system
down by consuming CPU time. Was I a contributor to this problem?

thanks, Bryan

 
 
 
Top

1. Ksh: Using 'wait' to parallelize tasks

I am reading from 2 tape drives in a shell script and I want to do this in
parallel since they really dont depend on each other.

I am doing something like

#!/bin/ksh
mt -f /dev/rmt/0 rewind
tar -xvf /dev/rmt/0 ..... &

mt -f /dev/rmt/1 rewind
tar -xvf /dev/rmt/1 .... &

wait
echo Done

The 'wait' command should wait for both the tars to complete and then
continue, right?

What I see instead is that both the tar commands complete fine, but the wait
never comes out. My 'echo Done' is never executed.

If I do this for a trivial case like
#!/bin/ksh
echo 1
sleep 10&
echo 2
sleep 15&
wait
echo Done

This works fine, as expected.

Any help appreciated.

Thanks

2. Now that I've read the FAQ...

3. 'LDT alloctated for cloned task' message

4. RedHat 7 and 600au

5. Beowulf for 'normal' tasks?

6. ES1868 driver

7. How to get background task to not return prcess # and 'done' line

8. Web based security monitoring : Why

9. 'defunct' task deallocation or avoidance

10. how does 'group similar tasks' determine similarity?

11. 'top' output -> High CPU consumption when thread is in 'sleep' state

12. How to kill process which not killed by 'kill' ?


All times are UTC
Board index