GitLab

tryLock() is necessary inside InterprocessSyncFile. It also doesn't
make sense afterwards to make a dynamically constructed Mutex::Locker
that lives after the basic block is exited. So lock() and unlock()
have also been made public.

I've added comments to discourage the use of these methods directly
and use the Mutex::Locker where applicable.

This test fails now because there's no mutual exclusion among threads
in the implementation.

To fix compilation.

"define and implement (datasrc::memory::)ZoneUpdater class"

It is now ZoneWriter.

No changelog.

Conflicts:
	src/lib/datasrc/memory/Makefile.am

We try to put some data there and see it survived.

Changed an exception for unexpected problem and removed a comment about
assert.

Instead of several boolean variables.

See ticket #2366 for details.

Okayed by muks on jabber.

Note that no test checked this and I don't introduce any test
since I am pretty sure this code will no exist in any production
version of a resolver (since won't limit IN only).

(it is now sync.h, which was already included)

Acked on jabber by muks

Conflicts:
	src/lib/util/threads/tests/lock_unittest.cc

solaris's pthread_cond_destroy doesn't seem to fail reliably in this case
as the test expects.

by a bit ugly hack: we specialize some part of the destructor and make
a local copy of these variables so the tests can inspect them later.

 commit.
 commit.

to delete AbstractRunningQuery objects returned by forward()