Turn off the PR 49140 logging, because it itself makes the test fail.

As usual, ATF is actively interfering with test debugging. Almost all
runs in the past few days have failed this test with "stdo

Turn off the PR 49140 logging, because it itself makes the test fail.

As usual, ATF is actively interfering with test debugging. Almost all
runs in the past few days have failed this test with "stdout not
empty". In one run it timed out:
http://releng.netbsd.org/b5reports/i386/build/2016.11.22.06.51.14/test.html
but in this case ATF helpfully suppressed the log data.

Maybe if someone can figure out how to make the test hang reliably
then they can turn the logging on again and run it outside of ATF to
see what's happening.

In the meantime this problem is not likely to get fixed until we have
a less obstructive testing framework.

show more ...

As a debugging measure for PR 49141, log what this is doing as it runs
to stdout. Hopefully this will get reported when the test fails in the
testbed rather than just causing ATF to report that it pr

As a debugging measure for PR 49141, log what this is doing as it runs
to stdout. Hopefully this will get reported when the test fails in the
testbed rather than just causing ATF to report that it printed
unexpected output.

show more ...

More of previous.

If pthread_create fails, report the error instead of discarding it.

Update hardcoded fd expectations now that rump kernels open 0/1/2.
(since we exec, it's convenient to just assume the values of first 4 fds)

Enable the "send a lot of syscall requests before exec" code, since
it works now. (or at least works in my tests)

add test case for multithreaded client calling exec