Here, after getting the cannot fork: messages about three or four
times since booting (a little over two days with 2.1.65) they haven't
locked up the system. In one case, it caused a Makefile (building
gimp at the time) to abort, but I was able to rerun it from basically
where it left off.
In other instances, these haven't adversely affected the system. One
was (as I reported) sent back to root in a crontab message, and the
other I briefly saw 'sendmail: cannot fork out of memory' on my
root console screen.
I've got a P100 with 16 megs of RAM and ~64 megs of swap.
> Rik: if you are reading this, kswapd was chomping 99% CPU and I wasn't
> trying to do much aside from start netscape. I could watch it paint
I didn't notice that, but I'll look into it. At the time, netscape wasn't
running, but I did have one or two xterms up, compiling in one window,
grabbing news in the other, etc.
> --Craig
------------------------------------------------------------------------
David E. Fox Tax Thanks for letting me
dfox@belvdere.vip.best.com the change magnetic patterns
root@belvedere.sbay.org churches on your hard disk.
-----------------------------------------------------------------------