Quoting Philip Rowlands <[EMAIL PROTECTED]>:
This is still putting your whole system in doubt, I'm afraid. gdb and
shred aren't magic unkillable processes; there's no reason they should
be hanging on the second invocation. If there's a process unkillable in
state "D", try this to see where it's waiting:
ps -eo pid,wchan=WIDE-WCHAN-COLUMN -o comm
The problem was solved by patching shred, but if you say there is
something strange here, lets continue with the unpatched version.
I have executed shred first time, it has shown "segmantation fault".
I have executed it for the second time and the console is hanging, I
can type anything there but cannot terminate it. I have opened second
sesson in screen and here is the end of output form ps:
20648 wait4 bash
20669 pause screen
20670 - screen
20671 wait4 bash
20684 schedule_timeout mc
20686 wait4 bash
22742 down shred
22743 wait4 bash
22767 - ps
Unfortunatelly I do not undersand it :-). Whar does it mean?
Best regards,
Adam
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
