Add a simple test of recovery -- on timed runs, the monitor thread
optionally indirects through a NULL and core dumps, then we verify
the object.
Clean up run reporting.
Add configuration options for log archive and pre-allocation, currently
at 50% each.

Turn on logging all the time in the recovery test script.

Explode the configuration snprintf() for wiredtiger_open.

The test to check for configuration buffer overrun in WT_SESSION.create
was wrong, fix it.
Use the eviction server to write pages with READGEN_OLDEST set.

Even before the eviction trigger has been reached. This should mean
that we clear those pages out of cache earlier, and hopefully will
save application threads from doing the evictions (at least sometimes).
Check that handles are not being walked by eviction before discarding.

refs #1497
Remove version numbering from the pkg-config file.  We don't create
include files that are named by version.  Programs linked using -lwiredtiger
will follow the symlink to wiredtiger-a.b.c.so, so their referred library
name is forever stamped as wiredtiger-a.b.c.so, which won't conflict
even when we ship wiredtiger-a.b.d.so .
Refs #1458.
Skip test_schema03.py on Window since rlimits are unix specific
Add __wt_getenv to workaround caching in MSVC CRT's getenv implementation.
Merge pull request #1502 from markbenvenuto/win_test_schema03

Skip test_schema03.py on Window since rlimits are unix specific
Merge pull request #1504 from markbenvenuto/wt_getenv

Add __wt_getenv to workaround caching in MSVC CRT's getenv implementation
Fix a bug where a custom extractor terminate was being called twice.

Resolves issue #1503.

Clarify the custom extractor and collator terminate documentation while
I'm here.
Merge branch 'develop' into evict-trickle
Merge pull request #1506 from wiredtiger/extractor-terminate

Fix a bug where a custom extractor terminate was being called twice.
Only trigger the eviction server to look for pages that would force eviction if regular eviction either fails or does an in-memory split.
Eviction should do update-restore if upper layers are trying to force out a page, regardless of its size.  Also, only look at ref->page after checking for exclusive access.  It is possible (but very unlikely) that a child page pointer could be replaced in the window where we are checking hazard pointers.
Make the cache bytes-written and bytes-read match, both should
ignore compression. Reference #1505.
Avoid EBUSY returns to verify and salvage caused by checkpoints.  The "fix" involves blocking checkpoints while salvage or verify are in progress.

refs #1404, SERVER-16457
Have extractor configuration checking match collator.

Clean up - no intended functionality change.
Merge pull request #1507 from wiredtiger/extractor-none-config

Have extractor configuration checking match collator.
Revert some debugging changes.