This only seems to happen on FreeBSD-3.2. During the configure test: 'Checking for working vfork...' FreeBSD *sometimes* seems to lock up. Doing a 'killall conftest' works, but the test failed and vfork is not used (configure does not fail, so i assume this). This is particularly bothering the FreeBSD 3.2 tinderbox (shadowmere), and my machine (which makes nightly builds). This seems to happen only once in a few times, but pretty often. I'm afraid I can provide no more specific information.

There is not much I can do about this. My 3.1 Tinderbox machine (angelus) seems not to have any trouble. Could this be an OS bug?

Is this still a problem? I'd like to close the bug, because there does not seem to be anything I can do about it. Have you discovered any new clues about this problem?

I've switched to 4.0-CURRENT, which _seems_ to solve the problem. I'll tell if it occurs again, but I agree that there probably is nothing that can be done about it.

I removed the check from configure.in a few weeks ago (on 8/22/99) as a grep of the tree showed that vfork() was not being used. Marking fixed.