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)
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.


No differences found