tdb2: suppress tdb1 backend logging when locking returns EINTR or EAGAIN
authorRusty Russell <rusty@rustcorp.com.au>
Wed, 31 Aug 2011 05:55:16 +0000 (15:25 +0930)
committerRusty Russell <rusty@rustcorp.com.au>
Wed, 31 Aug 2011 05:55:16 +0000 (15:25 +0930)
The TDB1 code logs multiple times on errors; we must prevent that in
the limited case where locking fails.  With TDB2, this can happen due
to the lock function attribute, where the user supplies replacement
locking functions which are allowed to return with errno EAGAIN or
EINTR for various special-effects.  Flooding the logs for this is
unfriendly.


No differences found