----- Original Message -----
I see this happen on our crash analysis machine:
crash> sys | fneep
sh: fneep: command not found
and then it sits, running up CPU time, until I hit ctrl-C 3 times.
--Guy
I didn't even try such a thing because Adrien's hanging command was seemingly
foolproof:
For completeness the command that was being run was looking like
this:
(gdb) p pc->orig_line
$26 = "log | grep -A1 'some string' >> /some/file",
'\000' [...]
Anyway, let me tinker with your example.
Thanks,
Dave