Well, that means the system runs out of resources when running the test. You're
probably running out of open files or RAM while the test is running. Try running
a top in
another window before you start it, to see if you can see what's being used. If
you're on
OpenBSD, 'systat vm' might be a better indicator of what's going on. Keep an eye
on
the fork number. If it shoots up, you might also be spawing processes too fast.
--Doug
When attempting to install Courier, everything has gone well so
far. I ran .configure, and make without any problems. However, when
I run make check, this "fork: Resource temporarily unavailable"
message just continues to loop.
I searched the archive for the list, and only saw it once and the
suggestion for resolution was to check system resources. I've done
that, made sure there is enough of everything, so I'm not sure that
is what the problem is here.
Thanks in advance,
Keith
...
Making check in userdb
Making check in authlib
Making check in waitlib
./testwait
fork: Resource temporarily unavailable
fork: Resource temporarily unavailable
...
2 messages in net.sourceforge.lists.courier-usersRe: [courier-users] OpenBSD - Newbie ...
