> Seems to me that newer kernel (2.1.46) have bad problems with above
> error... Is someone else experiencing this? It is bad when running cvs
>
> (in way export CVSROOT=localhost:/...), cvs can not fork sometimes and
>
> it is _bad_.
I first encountered this problem in 2.1.38 at various times, one them
was
while trying to read a man page. Free reported there was an adequate
amount of physical & swap space memory left so lacking memory
shouldn't be the cause.