Bizarre

Ever seen cp on Unix going in to an infinite loop and never returing while copying a tiny 2k file? I had no idea it was possible until half an hour ago. Came back to my desk after a nice cappucino and saw this:

PID USER       PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
1563 lolss     25   0  2728  832  640 R  100  0.0   0:12.99 cp

It never returns (had to kill it after waiting ten minutes)

I have no idea what's wrong. Only happens when I do the copy using system in a C-program that is started with my new favorite application, zzuf.

Deutsche Shrinkage