chiark / gitweb /
The initial rescan now blocks any client connections. This means that
authorRichard Kettlewell <rjk@greenend.org.uk>
Thu, 22 Nov 2007 11:35:34 +0000 (11:35 +0000)
committerRichard Kettlewell <rjk@greenend.org.uk>
Thu, 22 Nov 2007 11:35:34 +0000 (11:35 +0000)
commit1a4a6350a9033f0c2d1e2b7e6c1a029bdaa46da6
tree0e4c19cddd3873abb895546bd3f9f3eb2ac8b309
parentfc9c24e3ebb095d05e2d140526289c622d6e5504
The initial rescan now blocks any client connections.  This means that
a deadlock is unlikely to arise in the initial scan.  It also means
that the server is not usable for a short period after startup (or
quite a long period after initial startup, but that's less of a
problem).

The tests now take advantage of this by waiting until the socket
appears before assuming the daemon has started.
server/disorderd.c
server/trackdb.c
tests/alltests
tests/dtest.py
tests/nothing.py
tests/version.py