On Mon, Jan 12, 2004 at 12:23:27PM -0800, Andrey Petrov wrote:
> I'd try more recent -current, there was similarly appearing problem fixed.

But there is still the "{nano}sleep() never returns" problem, which might
look this way too. Everything still works in this case, machine answers ping
etc, but anything sleeping just hangs unkillable forever.

If this is your problem and you have a shell open when this happens, you
should still be able to run "ls" for example, but not "top".

Unfortunatley this problem is pretty unclear and hard to reproduce, though
rumors say high network load could provoke it earlier.

Martin