> I "killed" my kernel (it was just swapping and otherwise irresponsive)
> with just aborting rsync v2.5.2.
My followup didn't make it, so here's a quick resend:
in that rsync version, after ^C, not all threads are killed, and the
remaining one wreaks havoc and eats all memory. NOT A KERNEL PROBLEM,
please apologize. (Running ulimit -v 30000 before or softlimit on rsync
cures this, obviously, to prevent the remaining runaway thread from
eating all memory.)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/